Answer: Workspace owners manage dots access through workspace defaults and custom roles: keep the workspace default off and assign a custom role to selected groups, then review permissions such as Use dots in Permissions. Check every role assigned to a member, since if one role grants access, turning it off in another role won't remove it. Status: Confirmed Entry: tool/chatgpt/admin-and-enterprise/configure-dots-role-based-access Revision: 5 Digest: sha256:3a3db193d90fedc3 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:49:45Z Last changed: 2026-11-20T13:37:47Z (local computer access: — → Local computer access requires a separate admin opt-in) Last verified: 2026-11-20T13:37:47Z Next check: 2026-11-21T13:37:47Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of access method | workspace defaults and custom roles | [1] | 2026-11-20 recommended setup | keep the workspace default off and assign a custom role to those groups | [1] | 2026-11-20 role check warning | if one role grants access, turning it off in another role won't remove it | [1] | 2026-11-20 key permission | Use dots | [1] | 2026-11-20 navigation path | Admin Console | [1] | 2026-11-20 workspace default setting | Use dots | [1] | 2026-11-20 local computer access | Local computer access requires a separate admin opt-in | [1] | 2026-11-20 Sources: [1] OpenAI. "Manage dots permissions and capabilities". https://learn.chatgpt.com/docs/enterprise/dots-admin-guide.md Role: primary. Accessed: 2026-11-20T13:37:47Z Quote: "Workspace owners manage access through workspace defaults and custom roles." (Supports: access method) Quote: "To give selected groups access, keep the workspace default off and assign a custom role to those groups." (Supports: recommended setup) Quote: "if one role grants access, turning it off in another role won't remove it" (Supports: role check warning) Quote: "**Use dots**: Allow members to use dots." (Supports: key permission) Quote: "Open **Admin Console** > **Permissions**." (Supports: navigation path) Quote: "enable **Use dots** if it should be available by default; otherwise grant access through a custom role." (Supports: workspace default setting) Quote: "Local computer access requires a separate admin opt-in" (Supports: local computer access) Snapshot SHA-256: 8d4f4ddf911a0ecb76cbda0a68520df2281e91f975a213bc9d1713825fedd05b (captured 2026-11-20T13:37:48Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:37:47Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:37:47Z Last attempt: 2026-11-20T13:37:47Z Notes and limitations: Extracted automatically from a single official source (section "1. Configure role-based access"). Related: https://latestn.com/tool/chatgpt/admin-and-enterprise/configure-outlook-label-exclusions How do I configure Outlook email sensitivity-label exclusions in ChatGPT? https://latestn.com/tool/chatgpt/admin-and-enterprise/configure-shared-drive-access How do I configure which Google Drive shared drives ChatGPT can access in my workspace? https://latestn.com/tool/chatgpt/admin-and-enterprise/configure-teams-access How do I configure which Microsoft Teams teams are allowed or blocked in ChatGPT? https://latestn.com/tool/chatgpt/admin-and-enterprise/compliance-platform-access-patterns What are the two access patterns supported by the ChatGPT Compliance Platform? https://latestn.com/tool/chatgpt/admin-and-enterprise/configure-approvals-native-app-access How do I configure browser approvals or control native application access in ChatGPT Enterprise? https://latestn.com/tool/chatgpt/admin-and-enterprise/configure-company-access How do I configure company access for @ChatGPT in Slack or Microsoft Teams? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:37:47Z | changed | local computer access: — → Local computer access requires a separate admin opt-in | [1] 2026-11-20T13:37:47Z | changed | workspace default setting: — → Use dots | [1] 2026-11-20T13:37:47Z | changed | navigation path: — → Admin Console | [1] 2026-11-20T13:37:47Z | changed | key permission: — → Use dots | [1] 2026-11-20T13:37:47Z | changed | role check warning: — → if one role grants access, turning it off in another role won't remove it | [1] 2026-11-20T13:37:47Z | changed | recommended setup: — → keep the workspace default off and assign a custom role to those groups | [1] 2026-11-20T13:37:47Z | changed | access method: — → workspace defaults and custom roles | [1] 2026-11-20T13:37:47Z | changed | Final step: Save, then check access for an intended member. → — | [1] 2026-11-20T13:37:47Z | changed | Default setting: Use dots → — | [1] 2026-11-20T13:37:47Z | changed | Navigation path: Admin Console → — | [1] 2026-11-20T13:37:47Z | changed | Key permission: Use dots → — | [1] 2026-11-20T13:37:47Z | changed | Recommended approach: keep the workspace default off and assign a custom role to those groups → — | [1] 2026-11-20T13:37:47Z | changed | Access method: Workspace owners manage access through workspace defaults and custom roles. → — | [1] 2026-11-19T13:28:14Z | changed | Final step: — → Save, then check access for an intended member. | [1] 2026-11-19T13:28:14Z | changed | Default setting: — → Use dots | [1] 2026-11-19T13:28:14Z | changed | Navigation path: — → Admin Console | [1] 2026-11-19T13:28:14Z | changed | Key permission: — → Use dots | [1] 2026-11-19T13:28:14Z | changed | Recommended approach: — → keep the workspace default off and assign a custom role to those groups | [1] 2026-11-19T13:28:14Z | changed | Local computer access: Local computer access requires a separate admin opt-in → — | [1] 2026-11-19T13:28:14Z | changed | Default capability setting: Use dots → — | [1] 2026-11-19T13:28:14Z | changed | Admin path: Admin Console → — | [1] 2026-11-19T13:28:14Z | changed | Permission to review: Use dots → — | [1] 2026-11-19T13:28:14Z | changed | Role conflict note: if one role grants access, turning it off in another role won't remove it → — | [1] 2026-11-19T13:28:14Z | changed | Recommended setup: keep the workspace default off and assign a custom role to those groups → — | [1] 2026-11-19T13:28:14Z | changed | Access method: workspace defaults and custom roles → Workspace owners manage access through workspace defaults and custom roles. | [1] 2026-11-18T13:31:41Z | changed | Local computer access: — → Local computer access requires a separate admin opt-in | [1] 2026-11-18T13:31:41Z | changed | Default capability setting: — → Use dots | [1] 2026-11-18T13:31:41Z | changed | Admin path: — → Admin Console | [1] 2026-11-18T13:31:41Z | changed | Permission to review: — → Use dots | [1] 2026-11-18T13:31:41Z | changed | Role conflict note: — → if one role grants access, turning it off in another role won't remove it | [1] 2026-11-18T13:31:41Z | changed | Recommended setup: — → keep the workspace default off and assign a custom role to those groups | [1] 2026-11-18T13:31:41Z | changed | Access method: — → workspace defaults and custom roles | [1] 2026-11-18T13:31:41Z | changed | admin console path: Admin Console → — | [1] 2026-11-18T13:31:41Z | changed | custom rules permission: Use custom rules for dots → — | [1] 2026-11-18T13:31:41Z | changed | local access permission: Allow local computer access → — | [1] 2026-11-18T13:31:41Z | changed | messaging permission: Add dots to Slack and Microsoft Teams → — | [1] 2026-11-18T13:31:41Z | changed | permission to use dots: Use dots → — | [1] 2026-11-18T13:31:41Z | changed | role conflict warning: if one role grants access, turning it off in another role won't remove it → — | [1] 2026-11-18T13:31:41Z | changed | targeted access approach: keep the workspace default off and assign a custom role to those groups → — | [1] 2026-11-18T13:31:41Z | changed | access method: workspace defaults and custom roles → — | [1] 2026-11-17T14:01:43Z | changed | admin console path: — → Admin Console | [1] 2026-11-17T14:01:43Z | changed | custom rules permission: — → Use custom rules for dots | [1] 2026-11-17T14:01:43Z | changed | local access permission: — → Allow local computer access | [1] 2026-11-17T14:01:43Z | changed | messaging permission: — → Add dots to Slack and Microsoft Teams | [1] 2026-11-17T14:01:43Z | changed | permission to use dots: — → Use dots | [1] 2026-11-17T14:01:43Z | changed | role conflict warning: — → if one role grants access, turning it off in another role won't remove it | [1] 2026-11-17T14:01:43Z | changed | targeted access approach: — → keep the workspace default off and assign a custom role to those groups | [1] 2026-11-17T14:01:43Z | changed | access method: — → workspace defaults and custom roles | [1] 2026-11-17T14:01:43Z | changed | Default capability setting: Use dots → — | [1] 2026-11-17T14:01:43Z | changed | Permission for custom rules: Use custom rules for dots → — | [1] 2026-11-17T14:01:43Z | changed | Permission for local computer: Allow local computer access → — | [1] 2026-11-17T14:01:43Z | changed | Permission for messaging channels: Add dots to Slack and Microsoft Teams → — | [1] 2026-11-17T14:01:43Z | changed | Permission to use dots: Use dots → — | [1] 2026-11-17T14:01:43Z | changed | Recommended approach for selected groups: keep the workspace default off and assign a custom role to those groups → — | [1] 2026-11-17T14:01:43Z | changed | Access method: workspace defaults and custom roles → — | [1] 2026-11-13T03:49:45Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/chatgpt/admin-and-enterprise/configure-dots-role-based-access/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/chatgpt/admin-and-enterprise/configure-dots-role-based-access POST: https://latestn.com/dispute/tool/chatgpt/admin-and-enterprise/configure-dots-role-based-access with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/chatgpt/admin-and-enterprise/configure-dots-role-based-access?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I configure role-based access for dots in a ChatGPT Enterprise workspace? Revision 5, last verified 2026-11-20T13:37:47Z. https://latestn.com/tool/chatgpt/admin-and-enterprise/configure-dots-role-based-access (accessed 2026-11-21T10:07:26Z). @misc{LatestN_tool_chatgpt_admin_and_enterprise_configure_dots_role_based_access_r5, title = {How do I configure role-based access for dots in a ChatGPT Enterprise workspace?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/chatgpt/admin-and-enterprise/configure-dots-role-based-access}}, note = {Revision 5; digest sha256:3a3db193d90fedc3; last verified 2026-11-20T13:37:47Z; accessed 2026-11-21T10:07:26Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/chatgpt/admin-and-enterprise/configure-dots-role-based-access