Overview

Workspace administrators can manage plugins, marketplaces, and included apps in Admin Console. Select the intended ChatGPT workspace and open Plugins. Review installation, app access, actions, provider permissions, and content restrictions. You can also manage apps from the Manage Legacy Apps setting within the plugins page.

For plugin installation, see: Plugins in ChatGPT and Codex.

Admin controls

A plugin can include skills, apps, and app templates. Plugin installation and underlying app access are separate controls.

Default behavior by plan

ChatGPT Enterprise and Edu

New Enterprise and Edu workspaces start with a selected set of apps enabled. These defaults do not change existing workspace settings and do not apply to Healthcare workspaces.

In general, new plugins and apps are disabled by default, and administrators can review and change availability. Go to Admin Console, select the intended ChatGPT workspace, and open Plugins. For legacy app workflows, use the retained Apps page described in the overview.

Note that plugins bundle apps and skills - disabling an underlying app blocks the app-backed capability, but does not necessarily uninstall the plugin or remove skills that do not depend on that app.

Enterprise and Edu admins can use RBAC for plugin installation and app access. Those controls are evaluated separately: a member may have a plugin installed but still be unable to use an included app.

ChatGPT Business

In ChatGPT Business, apps are enabled by default, and administrators can change workspace-wide app availability. Go to Admin Console, select the intended ChatGPT workspace, and open Plugins. Review the app or its included plugin there, or use the retained Apps page for legacy workflows. Disabling an app does not necessarily uninstall a plugin or remove its skill-only capabilities.

Role-based access control

Enterprise and Edu workspaces may assign eligible plugins to custom roles when role-level plugin controls are available. Users can access plugins enabled for their workspace and applicable role. If a plugin shows Disabled by admin, its workspace settings, its applicable role settings, or an included app may be preventing access.

Plugins that include required apps inherit those apps’ role and action settings. If a member's role cannot access a required app, the plugin cannot use that app-backed capability for that member. Workspace plugin controls can also determine whether a plugin is Available or Installed for a role.

Manage multiple plugins

Workspace administrators on ChatGPT Business, Enterprise, Healthcare, and Edu can change availability for up to 25 plugins at a time. Role-specific controls require a workspace with role-based access control enabled.

1. Open Admin console and select the intended ChatGPT workspace.

2. Open Plugins and select the checkboxes for the plugins you want to change.

3. Select Edit, then choose Available for installation, Installed for workspace, Customize by role, or Disable, depending on the change you want to make.

4. For Customize by role, use Change availability for to select Workspace default or a custom role. Use Set availability to choose the intended setting.

5. Review the affected plugins and any dependency information, then confirm the change.

6. Review the result for each plugin. If a result is unsuccessful or unclear, check that plugin's saved settings before trying again.

Available for installation lets members install the selected plugins. Installed for workspace installs them by default and keeps role overrides. Disable changes the workspace default to disabled. In a custom role, Workspace default inherits the workspace setting.

Review required apps and their permissions separately. For help with incomplete changes, see: Troubleshooting plugins and apps in ChatGPT.

Manage plugin and app access

App access controls who can use a connected app in the workspace. App permissions control when ChatGPT asks before using an app.

Role-specific app access in this section applies to Enterprise and Edu workspaces. ChatGPT Business administrators manage whether an app is enabled for the workspace.

To manage who can use an app:

1. Go to Admin Console, select the intended ChatGPT workspace, and open Plugins.

2. Select the plugin and review the included app’s access settings.

3. When Role access is available, select the applicable roles and save when prompted.

For legacy app workflows, use the retained Apps administration page described in the overview.

To manage which apps a role can use:

• Go to Workspace settings > Permissions & roles.

• Select Custom roles.

• Select the role you want to edit.

• Scroll to the Plugins & connected data section.

• Turn on Allow members to use plugins, or Use plugins when that is the label shown, to allow plugin and app use for the role. FedRAMP workspaces may show Use apps.

• Use Select to choose specific apps for that role.

Restrict connected app accounts by verified domain

ChatGPT Enterprise organizations can request a restriction that limits where accounts using a verified company email domain can connect to supported apps. Contact OpenAI Support to request this be enabled. Include your verified company domain and the names of the apps your organization would like to restrict.

Once enabled, the restriction blocks new connections to supported apps when the connected account uses the restricted domain and the ChatGPT workspace is outside your organization’s authorized workspaces. Use an authorized workspace to connect the account.

The restriction applies only to the supported apps listed below. Existing app connections are not automatically disconnected. Verifying a domain alone does not turn on the restriction, and domain claiming that restricts personal ChatGPT accounts is not required.

Example: Acme verifies acme.com and has OpenAI Support enable the restriction for that domain. Alice opens her personal ChatGPT workspace and tries to connect a supported app using an app account with the email address alice@acme.com. The new connection is blocked. She must switch to an authorized Acme workspace.

This restriction limits new connections using your verified company email domain to your organization’s authorized ChatGPT workspaces. To limit which email domains can connect to an app inside your workspace, configure Manage domains separately for that app, where available. Enabling the verified-domain restriction does not turn on Manage domains.

For verification requirements, see: Verifying your domain for OpenAI identity.

Apps supported for verified-domain restrictions

Restrict app accounts with Manage domains

Workspace owners and admins can use Manage domains to choose which account email domains members can use when connecting an app to the workspace. Configure this separately for each enabled app that offers the setting.

1. Go to Admin Console and select your workspace.

2. Open Plugins, then open the plugin that contains the app.

3. Find the app and select Manage domains. If the page links to another plugin’s settings, open those settings first.

4. Add the account email domains you want to allow, such as acme.com.

5. Select Save.

For apps managed through Manage legacy apps, open that page from Plugins, then open the enabled app’s ••• menu and select Manage domains.

Leaving the allowed-domain list empty allows accounts from all email domains to connect.

If you encounter an error configuring Manage domains, contact OpenAI Support.

Add apps and plugins

When enabling a new app, review its workspace availability and any supported action controls. In Enterprise and Edu workspaces, assign eligible roles when role-based controls are available.

App templates follow the same admin governance model after publishing. Workspace admins and owners review the template-generated draft app, publish it when ready, and manage workspace availability, supported actions, and app permissions from the relevant plugin detail page. Enterprise and Edu admins can also configure role-scoped access when available.

For template setup, see: ChatGPT app templates.

Go to Admin Console, select the intended ChatGPT workspace, and open Plugins. Select a plugin to review its skills, included apps, and Installation policy. Available lets eligible members install the plugin, while Installed installs it by default. Where role-based controls are available, administrators can configure the policy for eligible roles. FedRAMP workspaces use the Apps administration page.

Plugins with required apps inherit those apps’ role and action settings. The required apps must be enabled for the affected role. Review other settings on the included app separately. Depending on the app state, admins may see Enable, Publish, Edit app configuration, or Disable.

Admins can configure a workspace-wide app permission and, when supported, a different setting for an individual app. The standard workspace-wide selector does not offer Allow all actions, although existing policy configurations can differ.

For permission details, see: Managing app permissions in ChatGPT.

App action controls

Role access controls who can use an app. Actions controls what the app can do. Permissions controls when ChatGPT asks before using an app.

These app permissions apply to ChatGPT conversations. Workspace Agents use per-agent controls set by the agent's builder to determine which app actions are available and when end users are asked to approve them. For agent behavior, see: ChatGPT Workspace Agents for Enterprise and Business.

Under Actions, enable the supported Read actions or Write actions you want to allow. Under New actions, select:

• Enable all new actions

• Only enable new read actions

• Disable new actions

Disable new actions applies only to actions introduced later; it does not disable actions that were already enabled.

Some apps do not offer configurable Actions or New actions controls. For those apps, admins can manage app access but cannot individually configure unavailable action controls.

Provider approval, OAuth scopes, and ChatGPT action settings are separate checks. Approving a provider scope does not automatically enable a new action, and changing a future-action policy does not remove existing provider consent. Some changes may require a user to reconnect or reauthorize the app.

To change the workspace default app permission:

• Go to Workspace settings.

• Open General and find Settings.

• Under Plugin permissions, select the workspace-wide approval setting.

To set a different permission for an app:

• Go to Admin Console, select the intended ChatGPT workspace, and open Plugins. Select the plugin that includes the app. If Plugins is unavailable, use the Apps administration page.

• In the plugin’s Apps section, open the included app’s Permissions control. In the older Apps view, use the app’s available permission controls.

• Select Workspace default or another available permission.

• Select Save if the interface asks you to confirm the change.

Available options depend on the workspace and app:

• Always ask: ChatGPT asks before reading app information or making changes.

• Allow read actions: ChatGPT can read app information without asking but asks before making changes.

• Allow low-risk actions: ChatGPT automatically approves low-risk actions. Higher-risk actions may require confirmation or be denied.

• Allow all actions: When supported for an individual app, ChatGPT can perform available actions without additional prompts. This option carries elevated risk and is not offered in the standard workspace-wide selector.

These settings do not override action controls, provider authorization, workspace restrictions, or safety protections.

For details, see: Managing app permissions in ChatGPT.

Manage Google Drive actions

Google Docs, Sheets, and Slides actions are now available through the Google Drive app. Standalone Google Docs, Sheets, and Slides apps are no longer listed separately. Users should connect Google Drive for Docs, Sheets, and Slides access.

For ChatGPT Enterprise and Edu, these unified Google Drive actions are off by default until a workspace administrator enables them. For ChatGPT Business, they are on by default. After enablement, Google Workspace administrators may need to reauthorize updated Google Drive scopes before users can use these actions or new users can connect. If users cannot connect to Google Drive, check your Google Workspace scope authorizations for Google Drive, Docs, Sheets, and Slides. Confirm that all actions in the app have scopes that have been authorized, or turn off actions you do not want to authorize.

Administrator-managed and individually authorized app sync are no longer available. Members can connect Google Drive for live access to supported files and actions.

Manage content access

Workspace owners and admins can use Safety & Security Controls for supported apps. For Google Drive, Microsoft Teams, and Outlook Email, these controls are available in Enterprise workspaces where enabled. These controls restrict content accessed through the live app. Provider permissions, app access, and enabled actions still apply.

• Google Drive: Allow or block whole shared drives and control Allow My Drive separately. These controls do not provide folder, individual-file, user/group, or Drive-label exclusions.

• SharePoint: Allow or block supported site collections and exclude selected sensitivity labels. For setup, see: Managing SharePoint site access and sensitivity-label exclusions.

• Microsoft Teams: Allow or block teams by their Microsoft 365 group IDs and exclude teams with selected sensitivity labels. Team rules cover their owned channels; they do not block ordinary one-to-one, group, or meeting chats.

• Outlook Email: Exclude messages with selected sensitivity-label GUIDs. Add each sublabel separately. This setting does not independently inspect sensitivity labels inside attachment files.

1. Open Admin Console and select your ChatGPT workspace.

2. Open Plugins and select the plugin that contains the app.

3. Open the app's Safety & Security Controls, where available.

4. Review and change the supported controls.

5. Select Save.

6. Test a permitted item and a restricted item with a fresh request.

For provider connection and permission requirements, see: Google Drive setup, SharePoint setup, Microsoft Teams setup, and Outlook Email setup.

For setup, see the Google Drive controls guide, Microsoft Teams controls guide, and Outlook Email label-exclusions guide.

Review access after changing a policy

Review workspace app access, enabled actions, and permissions in the connected service as separate checks.

• Confirm which roles or groups can use the app.

• Confirm that the member has connected the intended provider account and can access the item in that service.

• Review saved content restrictions for the app. A member's provider permissions do not override a workspace restriction.

• Ask the member to test a permitted item and a restricted item with fresh requests after saving a change.

For Google Drive, an explicitly empty Allowed drives list blocks every shared drive. Allow My Drive is a separate setting. For Teams, clearing the team lists removes the restrictions imposed by those group lists; other configured controls still apply. Review the intended result before saving.

Administrator-managed sync is no longer available. Review the current saved Safety & Security Controls policy for each app. Don't rely on former sync selections or indexing status alone to verify live app access.

Resolve inconsistent or unavailable settings

If a setting says an app is enabled but access is still blocked, check the affected member and app in the intended workspace:

• Confirm workspace app access and the member's applicable role access. Plugin installation alone does not establish access to an included app.

• Review the specific app actions that are enabled and the app's permission setting.

• Confirm the connected provider account, its organization, and its access to the item in the source service.

• Reopen the saved content restrictions and compare them with the intended policy.

For Microsoft apps, also ask your Microsoft Entra administrator to verify the current grant in the correct organization. A recorded approval in ChatGPT is not a substitute for that grant.

If saved settings still contradict each other, an expected action is missing, or a selector is unavailable, contact OpenAI Support. Include the workspace plan, affected role and app, exact error, and screenshots of the conflicting settings. Don't broaden provider permissions or enable unwanted actions just to make a control available.

Microsoft apps permissions required

Some actions in the Outlook Email, Outlook Calendar, Microsoft Teams, and SharePoint apps require Microsoft Graph permissions that a Microsoft Entra administrator must grant for the organization. A ChatGPT workspace owner or admin and a Microsoft Entra administrator may be different people, so coordinate with the person who can grant organization-wide consent.

Review permissions in ChatGPT

Go to Admin Console, select the intended ChatGPT workspace, and open Plugins. If you see Configure Microsoft permissions there, select it to review the combined permission request for your enabled Microsoft apps.

For the retained Apps settings page, follow these steps for the Microsoft app you want to review:

1. Sign in to ChatGPT as a workspace owner or admin.

2. Open Apps in your workspace settings and select the Microsoft app you want to review.

3. Open the app’s more options menu (•••) and select Manage app.

4. Select Microsoft permissions when that option is available.

5. Review each Microsoft Graph permission and the ChatGPT actions listed beneath it. Upcoming means an action is included for advance permission review but is not currently available. Approved means the permission was included in the last successful approval flow completed through ChatGPT for that app and workspace.

6. Review the permissions required by your selected app actions. Required permissions remain selected and can't be turned off in this review. To remove one from the request, first disable every selected action that requires it, including actions in other enabled Microsoft apps when reviewing a combined request.

7. Turn optional permissions on or off when their switches are available. Reopen the permission review and confirm the request before continuing.

Complete the request in Microsoft Entra

1. Select Review permissions in Microsoft Entra. If Microsoft Entra does not open, allow pop-ups for ChatGPT and try again.

2. Sign in with a Microsoft Entra administrator account that can grant organization-wide consent.

3. Confirm that the correct organization and the verified ChatGPT / OpenAI, L.L.C. application are shown.

4. Review the selected permission request. The Microsoft Entra confirmation screen does not provide per-permission checkboxes: select Accept to grant the complete selected request, or select Cancel to make no change.

5. Return to ChatGPT and confirm that the approval flow completed.

Review the action settings for every enabled Microsoft app. Microsoft permissions are granted to the Entra tenant and OpenAI application, and a single permission request in ChatGPT may cover multiple apps.

After permissions are approved

Microsoft permission approval does not enable ChatGPT actions or connect an individual user’s Microsoft account. Workspace owners and admins must separately enable the actions they want to make available. Users may also need to connect or reconnect their Microsoft account after permissions change.

If an action still does not work, confirm that:

1. The action is enabled in the ChatGPT workspace’s app settings.

2. The permission grant still exists in Microsoft Entra.

3. The user’s Microsoft connection has been created or refreshed with the required permissions.

If an Entra administrator later changes or revokes the grant directly in Microsoft, review the grant in Entra and rerun the ChatGPT approval flow.

Review the following Help Center pages for the permissions required by each app:

• Outlook Email

• Outlook Calendar

• Microsoft Teams

• Microsoft SharePoint

Each app page describes the scopes required by that app. For the current permissions and associated actions, review the Microsoft permission request available in your workspace.

Custom apps

Workspace owners, administrators, and authorized members can create or add custom apps, subject to their plan and workspace policy.

When an app requires individual provider authorization, users connect an eligible account before using those features. Other apps can use no-auth access or an administrator-managed workspace connection.

Business, Enterprise, and Edu admins can refresh an existing published custom MCP app’s tool list from workspace app settings without recreating the app. The admin refreshing the tool list must have permission to manage the app and a valid connection to it. For tool-refresh and setup guidance, see: Connecting custom MCP servers in ChatGPT.

For a technical walkthrough of creating a custom MCP connector, see: Creating custom MCP apps.

Custom apps are not verified by OpenAI and are intended for developer use only. You should only add custom apps to your workspace if you know and trust the underlying application. For details, see: Custom app risks and safety.

• Apps may allow end users to share data, which could include protected health information (PHI), with third parties. You should ensure that your use of apps complies with your obligations under HIPAA.

Security and compliance

Security

OpenAI protects customer content within its covered services using encryption in transit and at rest. Depending on the app and workspace configuration, access may use an individual provider account, an administrator-managed connection, or another supported authorization method. Source permissions still apply.

OpenAI uses testing, monitoring, access controls, and layered safeguards to reduce prompt-injection and unauthorized-access risks. These measures do not eliminate third-party or prompt-injection risk. Review each app’s source permissions, enabled actions, access settings, and provider terms.

Healthcare workspaces and protected health information

When enabling an app in a healthcare-related workspace, you may see a warning about protected health information. Review your organization’s requirements and select I understand and accept these risks. Then select Continue.

Acknowledging this warning does not change your Business Associate Agreement or authorize the app to process protected health information.

The Epic plugin connects to patient-chart information in ChatGPT and Codex through the required Epic EHR app. An administrator must configure the organization’s Epic connection, enable the app for approved users, and confirm that each user signs in with their own Epic account. Existing workspace, Epic, and patient-chart permissions still apply.


Healthcare Public Data is a separate plugin for ChatGPT and Codex that searches public healthcare sources. Its apps do not access patient records, and public-data queries must not include patient identifiers or protected health information.

Model training and app data

By default, OpenAI does not use ChatGPT Business, Enterprise, or Edu workspace content, including information accessed through apps, to train its models. For current terms and applicable opt-ins, see: Enterprise Privacy.

Information included in chats or research outputs follows the applicable conversation, feature, and workspace-retention policies.

Data storage and residency

For data residency boundaries and instructions to check the configured region, see: Data residency and inference residency for ChatGPT.

Information sent to a connected third-party service is subject to that provider's storage, processing, privacy, and data-residency terms.

Data residency applies to in-scope customer content stored at rest for supported features. It does not mean that every processing step, system record, external integration, or third-party app remains in the selected region.

Compliance

ChatGPT Business administrators manage workspace settings and app availability; they do not automatically gain access to members’ ordinary private conversations. The Compliance Platform is available only to eligible Enterprise and Edu workspaces, subject to configuration and the administrator’s assigned permissions.

When available, app-activity records can include an app request and related response information. App-authentication records can show account connection and disconnection events. Retention depends on the applicable Compliance Platform endpoint, workspace retention settings, and any records exported by the organization.

Compliance API and app-log availability depend on the specific app, product, and workspace configuration. Confirm the supported export coverage for each app before relying on logs for compliance.

For documented app-log behavior, see the OpenAI Compliance Logs platform.

For current enterprise compliance guidance, see: OpenAI Compliance Platform for Enterprise and Edu Customers.