Overview
Plugins help Codex complete repeatable work by packaging the capabilities it needs for a specific workflow. A plugin can include workflow guidance, such as skills, and can also depend on approved apps that connect Codex to tools, data, or actions.
For Business, Enterprise, and Edu workspaces, plugin availability can depend on workspace settings, feature access, and the apps an admin has enabled. A plugin does not grant new access to data by itself. Users can only use app-backed capabilities when the connected app is available to them and they already have access to the underlying source system.
This article is for workspace admins, owners, and users who need to understand how plugins work and what needs to be enabled before a plugin can be used.
What is a plugin?
A plugin is a packaged capability for a workflow. Depending on the plugin, it may include:
Skills, which provide reusable instructions, prompts, and workflow patterns that help Codex complete a task.
Apps, which connect Codex to systems, data, and actions approved for your workspace.
App templates, which help an admin create or configure the app or connector the plugin needs.
Some plugins are broad, while others are built for a specific line of business, such as sales, data analytics, or internal operations. A line-of-business plugin may bring together several capabilities so users can complete a job without manually switching between separate tools.
A single plugin may have multiple skills and apps, allowing users to accomplish a wide variety of tasks. Admins and owners can enable some or all apps within a plugin, depending on organizational policy. For example, a sales-focused plugin might include multiple app-backed capabilities that support a sales workflow.
How plugins use apps
Many plugins depend on apps to reach external systems. For example, a plugin may need access to a workspace-approved app that connects to a repository, data warehouse, CRM, document store, or messaging tool.
Admins and owners control who can use those apps in ChatGPT or Codex. Depending on the app, admins and owners may also control:
Which users, groups, or roles can access it.
Whether it can read data only or also take actions.
Whether users must confirm actions before they run.
Whether sync, domain restrictions, source boundaries, or other app-specific settings apply.
Approving an app in ChatGPT does not override permissions in the source system. If a user cannot access a file, repository, record, workspace, or channel in the connected system, the plugin should not give them access to it through Codex.
Before users start with a plugin
Before asking members to use a plugin, check the plugin's requirements and confirm that the required app or connector is available in your workspace.
Open Workspace settings > Apps or the relevant plugin directory area in your workspace.
Find the app, connector, or template the plugin requires.
Review what system it connects to, what data it can access, and what actions it can take.
Assign access to the users, groups, or roles that should use the plugin.
If the app requires provider authentication, ask a test user to connect their account.
Run a low-risk test prompt to confirm the plugin works as expected.
If your workspace has a separate plugin directory, use that directory to review plugin-specific details. If plugin controls are not yet visible in your workspace, continue to manage the underlying apps or connectors through workspace app settings.
Plugins that include app templates
Some plugins may include an app template or depend on an app created from a template. App templates are not the same as a ready-to-use app. A workspace admin or owner may need to enter organization-specific configuration, create a draft app, publish it, and assign access before members can use the plugin.
If a plugin depends on an app template that has not been set up yet, members may need an admin to complete setup first. The plugin cannot use the app template by itself.
For more about template setup, see ChatGPT app templates.
Security and permission considerations
When reviewing a plugin, use the same review process you use for apps and connectors in ChatGPT.
Confirm what external system the plugin depends on.
Confirm whether the plugin can use read-only actions, write actions, or both.
Confirm whether action confirmation is required for sensitive actions.
Keep the first rollout limited to a pilot group when possible.
Review whether legal, security, privacy, data residency, or vendor approval is needed before expanding access.
Periodically review access after rollout.
Apps and connectors may have their own terms, privacy policies, and data residency commitments. Review those terms before enabling access for sensitive or regulated workflows.
Troubleshooting plugin access
I cannot find the plugin
Plugin availability can depend on your plan, workspace settings, rollout status, and feature access. If you expected to see a plugin and do not, ask your workspace admin or owner to confirm whether the plugin is enabled for your workspace.
The plugin says an app or connector needs setup
Ask a workspace admin or owner to review the required app or connector. The admin may need to enable it, create it from a template, publish a draft, or assign access before members can use the plugin.
The plugin cannot access the expected data
Check both ChatGPT workspace access and the source system. The user must have access to the app or connector in ChatGPT and must also have permission to the underlying content in the connected system.
The plugin cannot take an action
An admin may have limited the app or connector to read-only access, or the action may require confirmation. Ask the admin to review action controls, action confirmation settings, and any source-system permissions required for the action.
I do not have access to skills
Some plugin behavior may depend on workspace or feature availability. If a plugin is visible but does not work as expected, ask your admin or workspace owner to confirm whether the required plugin, skill, app, and connector capabilities are available for your workspace.