SpyBara
Go Premium

enterprise/apps-and-connectors.md 2026-08-14 22:00 UTC to 2026-08-15 01:01 UTC

This page contains 77 additions and 54 deletions.

2026
Mon 10 22:00 Sat 15 01:01 Thu 20 23:59 Sat 29 07:02

Plugin controls

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to the page URL.

Plugins package reusable workflows and can include skills and apps that connect to other tools. ChatGPT and Codex use the same public plugin directory on supported surfaces, while admins decide which plugins are available in their workspace. Learn more about plugins, skills, and apps and connectors.

A member can use a connector-backed capability only when the plugin and app are available to their role and they have access to the connected service.

Plugins work in Chat and Work across ChatGPT on the web, desktop, and mobile, in Codex in the ChatGPT desktop app, and through the Codex CLI plugin browser. They aren't available in the IDE extension.

To see how these controls fit with workspace roles and permissions, see Roles and workspace permissions.

Understand the capability chain

A plugin can span these control layers:

Layer What it determines Where to manage it
Availability Whether the plugin bundle is available to the user Workspace settings for supported web and desktop surfaces; the CLI plugin browser for CLI
Included skills Which reusable instructions the installed plugin contributes The plugin package and Skill controls
App access Whether users can use a connector-backed capability Workspace apps and Permissions & roles
Actions and permissions Which actions users can run and when ChatGPT asks before using the connector The connector's Action control and App permissions in Workspace apps
Service authorization Which external data and actions the authenticated identity can access The connected service and its identity provider
Runtime permissions What an agent can do after it receives data or a tool The runtime, sandbox, and approval controls for the active surface

Use these layers as a two-step rollout: first make the right plugins available, then configure the capabilities and permissions each workflow needs.

Step 1: Enable plugin availability

For supported web and desktop surfaces, workspace plugin controls determine which roles can use or install a plugin. The Codex CLI uses its own plugin browser for installation. See Build plugins for packaging and distribution.

Step 2: Manage capabilities

Making an app or plugin available in ChatGPT doesn't grant access to files, records, or actions in the connected service. Before troubleshooting or expanding access, check the member's workspace role and approved action settings. Then confirm the authenticated account or shared connection has the expected permissions in the connected service.

Plugins in ChatGPT and Codex can include connectors that search, retrieve, sync, or act on external systems. Plugin availability and the access and actions granted to each connector are separate controls.

Manage connector-backed capabilities from Workspace apps and Permissions & roles. Available controls let admins:

  • Enable apps or connectors and assign access by workspace role.
  • For connectors that support Action control, allow read-only actions or an approved custom set, including how the workspace handles newly added actions.
  • Set App permissions that determine when ChatGPT asks before using an app.
  • Keep access within the scopes and permissions granted by each connected service and authenticated user.

For current availability and procedures, see Admin controls, security, and compliance in apps.

Choose a focused initial set

Start with plugins that support a clear business need. Decide whether to make each plugin available to everyone, limit it to a role or pilot group, or require further review.

For each connected service, record the business owner, permitted data, approved read or write actions, authentication method, and a support or removal contact.

Before enabling write actions or publishing a new connected capability, verify its role scope and test with an account that has only the intended permissions in the connected service.

For a broad rollout, begin with categories teams use every day, such as email, calendar, and file or document systems. Use the Plugins Directory to confirm current availability and capabilities across supported ChatGPT and Codex surfaces.

Whatever the initial set, start with read actions. Before enabling write actions, identify the plugin owner, review connector scopes and service permissions, confirm data access, and document external effects and a recovery path.

Understand data flow and security

When ChatGPT uses an app or connector included with a plugin, it sends a request to the connected service and returns data or action results allowed by the authenticated user's permissions in that service.

ChatGPT handles connected app data in two ways:

  • Non-synced: ChatGPT processes data from Chat and deep research transiently and doesn't index it.
  • Synced: ChatGPT indexes selected connected content in advance. You can see whether an app supports sync on its plugin page.

The mode changes how ChatGPT indexes connected content; it doesn't replace normal chat-retention controls. ChatGPT conversations that use apps remain available through the Compliance API.

OpenAI's app guidance documents encryption in transit and at rest, per-user authorization, role and action controls, restricted network access for conversations that use apps, and no model training on information accessed through apps for Business, Enterprise, and Edu customers. When a request reaches a connected service, that service's scopes, retention, data residency, and other policies also apply.

See app security and compliance and apps with sync for current data-handling details. For locally configured MCP servers in the ChatGPT desktop app, Codex CLI, or IDE extension, see Codex MCP configuration.

Use current procedures and references