2 2
3> For the complete documentation index, see [llms.txt](https://learn.chatgpt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.3> For the complete documentation index, see [llms.txt](https://learn.chatgpt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to the page URL.
4 4
5Plugins package reusable workflows and can include skills and MCP servers that connect5Plugins help your team reuse instructions and work with information from connected
6to other tools. ChatGPT and Codex use the same public plugin directory on6apps. For example, a plugin can help prepare a weekly update using your team's
7supported surfaces, while admins decide which plugins are available in their workspace.7template and project documents. Members can use it again without adding the same
8Learn more about [plugins](https://learn.chatgpt.com/docs/plugins),8instructions to every conversation.
9[skills](https://learn.chatgpt.com/docs/skills-and-plugins), and
10[connected services](https://help.openai.com/en/articles/11487775).
11 9
10As an admin, you decide who can use each plugin and what its apps can do. This
11guide explains how to choose settings, test access, and help members when
12something doesn't work.
12 13
13 14
14 {"For workspace controls and data-handling guidance, see "}
15 [{"Admin controls, security, and compliance for plugins and apps"}](https://help.openai.com/articles/11509118)
16 {" in the Help Center."}
17 15
16 {"For setup, availability, and data handling, see the "}
17 [{"Help Center's plugin administration guide"}](https://help.openai.com/articles/11509118)
18 {"."}
18 19
19 20
20In this guide, **app** and **MCP server** refer to the same connected
21integration and are interchangeable terms. We use **MCP server** in the prose,
22but preserve **app** in UI labels such as **Workspace apps** and
23**App permissions**, and in CSV column names.
24 21
25A member can use an MCP server's capabilities only when the plugin and MCP server22See how plugin availability, roles, and groups work together.
26are available to their role and the authenticated account has access to the
27connected service. For a shared credential, the member also needs permission
28to use that credential; the external account can differ from their personal account.
29 23
30Plugins work in Chat and Work across ChatGPT on the web, desktop, and mobile,24<div
31in Codex in the ChatGPT desktop app, and through the Codex CLI plugin browser.25 class="not-prose my-4 overflow-hidden rounded-md bg-gray-900"
32They aren't available in the IDE extension.26 style="padding:56.25% 0 0 0;position:relative;"
27>
28 <iframe
29 src="https://player.vimeo.com/video/1238920850?badge=0&autopause=0&player_id=0&app_id=58479"
30 frameborder="0"
31 allow="autoplay; fullscreen; picture-in-picture; clipboard-write; encrypted-media; web-share"
32 referrerpolicy="strict-origin-when-cross-origin"
33 style="position:absolute;top:0;left:0;width:100%;height:100%;"
34 title="Managing plugins as a workspace administrator"
35 ></iframe>
33 36
34To see how these controls fit with workspace roles and permissions, see37
38<script src="https://player.vimeo.com/api/player.js"></script>
39
40<a id="choose-plugins-around-the-work-your-team-does"></a>
41
42## Choose plugins for your team's tasks
43
44A plugin can include skills, apps, or both:
45
46- **Skills** give ChatGPT instructions, templates, and reference material for a
47 task, such as preparing a brief or presentation.
48- **Apps** let ChatGPT work with tools and information in services such as
49 Google Drive or Slack. An app can only use the information and actions allowed
50 by its settings and the connected account's permissions.
51
52In the weekly update example, the skill supplies the reporting instructions and
53template. The app retrieves project documents the connected account can access.
54
55You can read a plugin's skills in its preview to check whether they suit the task.
56The preview doesn't let you edit the instructions or select individual skills
57from the plugin. See [Skill controls](https://learn.chatgpt.com/docs/enterprise/skills) for more guidance.
58
59<a id="choose-a-starting-set-of-apps"></a>
60<a id="choose-a-focused-initial-set"></a>
61
62Before choosing settings, decide who needs the plugin and whether their task
63involves reading information, changing it, or both. A plugin that one department
64uses every week may be optional for another.
65
66Give members a short description of when to use each approved plugin and one
67example request.
68
69<a id="understand-the-capability-chain"></a>
70
71## Understand what each control does
72
73Member permissions control what people can do with plugins. Installation
74settings control which plugins they can install or receive by default. App and
75account settings control access to connected information and actions.
76
77| What you want to control | Where to look |
78| ---------------------------------------------------------------------------- | -------------------------------------------------------------------- |
79| Who can use, upload, share, or publish plugins. | [Member permissions](#choose-what-members-can-do-with-plugins). |
80| Who can install a plugin and who gets it by default. | [Installation settings](#choose-installation-settings). |
81| Who can use an app and which actions it allows. | [App access and actions](#manage-app-access-and-actions). |
82| When ChatGPT asks before using an app. | The app's **Permissions** settings. |
83| Which files and records an account can access and which actions it can take. | Permissions in the connected service, such as Google Drive or Slack. |
84| Additional limits on content ChatGPT can access. | [Content restrictions](#review-content-access), where supported. |
85| What an agent can do on a computer or in a cloud environment. | [Environment permissions](#review-runtime-controls-and-hooks). |
86
87
88
89 {"For background on plugin security, read the "}
90 [{"App Security Whitepaper (PDF, June 2026)"}](https://cdn.openai.com/business-guides-and-resources/app-security-whitepaper.pdf)
91 {"."}
92
93
94
95## Choose what members can do with plugins
96
97Before choosing individual plugins, review member permissions. Open your
98workspace's **Permissions & roles** settings and search for **plugins**.
99Depending on your workspace, the controls include:
100
101| Member permission | What it allows |
102| -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
103| Use plugins | Use plugins and apps available to the workspace. |
104| Upload plugins | Create plugins by uploading plugin ZIP files. |
105| Upload plugins with custom MCP servers | Upload or update plugins that include custom connections to tools. Members still need permission to create or edit the plugin. |
106| Share plugins | Share plugins they own with people or groups, or anyone in the workspace with a link. |
107| Publish plugins to workspace | Add plugins they own to the workspace's plugin directory. |
108| Create plugins with MCPs | Use developer mode to create custom app connections. |
109
110Where role-based access control (RBAC) is supported, a role holds a set of
111permissions. Workspace owners can assign a role to a group so its members receive
112those permissions. For example, a team can use approved plugins while only the
113people maintaining them have permission to upload or publish them.
114
115These permissions are separate from each plugin's installation settings. Next,
116choose which plugins members can install or receive by default. For more on
117assigning roles and groups, see
35[Roles and workspace permissions](https://learn.chatgpt.com/docs/enterprise/roles-and-workspace-permissions).118[Roles and workspace permissions](https://learn.chatgpt.com/docs/enterprise/roles-and-workspace-permissions).
36 119
37To configure plugin authentication for supported workspace120<a id="step-1-enable-plugin-availability"></a>
38experiences, see [Workspace connections](https://learn.chatgpt.com/docs/enterprise/shared-connections).121
39Installing a plugin for everyone doesn't, by itself, provide a shared account.122## Choose installation settings
123
124Open [Admin console](https://admin.openai.com),
125select your workspace, and open **Plugins**. The bulk edit menu offers these
126installation settings:
127
128| Setting | What it changes | When to consider it |
129| -------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------- |
130| Available for installation | Members can install the plugin. | Plugins that members choose based on their work. |
131| Installed for workspace | Installs the plugin by default and keeps any role-specific settings. | A plugin the team uses regularly. |
132| Customize by role | Sets availability for a custom role where supported. | A plugin for a particular team or responsibility. |
133| Disable | Changes the workspace default to disabled. | A plugin you no longer want available by default. Review role overrides too. |
134
135Where per-plugin role settings are supported, **Workspace default** uses the
136workspace setting. For ordinary custom roles, **Off** means that role
137doesn't give access. A member may still get access through another role, so
138check all roles assigned to them, including those assigned through groups.
139
140For example, make a research plugin available for members to install when they
141need it. If role controls are available, install the weekly update plugin for the
142role assigned to the people who prepare those updates. Check their app access
143before asking them to use it.
144
145### Manage multiple plugins together
40 146
41Plugins in Sites let each visitor use their own connected accounts. Each147To change several plugins at once, select them and choose **Edit**. Use this only
42 plugin has a separate Sites permission, with defaults that depend on the148when the plugins need the same installation setting. Review who the change
43 workspace plan. See [Enable plugin use in149affects and which apps each plugin needs before confirming. If a change fails
44 Sites](https://learn.chatgpt.com/docs/enterprise/sites#enable-plugin-use-in-sites) to review plugin150or you're unsure whether it saved, check that plugin's setting before trying again.
45 defaults, change access, and troubleshoot tenant restrictions.
46 151
47## Understand the capability chain152For current limits and instructions, see the [Help Center's plugin administration guide](https://help.openai.com/en/articles/11509118-admin-controls-security-and-compliance-for-plugins-and-apps).
48 153
49A plugin can span these control layers:154To manage workspace plugins from a repository, see
155[Import and sync plugins from GitHub](https://learn.chatgpt.com/docs/enterprise/plugin-management). For installation on
156other versions of ChatGPT and Codex, see [Plugins](https://learn.chatgpt.com/docs/plugins).
50 157
51| Layer | What it determines | Where to manage it |158<a id="step-2-manage-capabilities"></a>
52| ----------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
53| Availability | Whether the plugin bundle is available to the user | [Workspace settings](https://chatgpt.com/admin/settings) for supported web and desktop surfaces; the CLI plugin browser for CLI |
54| Included skills | Which reusable instructions the installed plugin contributes | The plugin package and [Skill controls](https://learn.chatgpt.com/docs/enterprise/skills) |
55| MCP server access | Whether users can use an MCP server's capabilities | [Workspace apps](https://chatgpt.com/admin/ca) and [Permissions & roles](https://chatgpt.com/admin/settings) |
56| Actions and permissions | Which actions users can run and when ChatGPT asks before using its tools | The connection's **Action control** and **App permissions** in [Workspace apps](https://chatgpt.com/admin/ca) |
57| Service authorization | Which external data and actions the authenticated identity can access | The connected service and its identity provider |
58| Runtime permissions | What an agent can do after it receives data or a tool | The runtime, sandbox, and approval controls for the active surface |
59 159
60Use these layers as a two-step rollout: first make the right plugins available,160## Manage app access and actions
61then configure the capabilities and permissions each workflow needs.
62 161
63## Step 1: Enable plugin availability162Installing a plugin doesn't give members access to its apps or external data.
163You also need to allow the required apps. If an app requires an account, that
164account must have permission to access the information or take the action in the
165connected service.
64 166
65For supported web and desktop surfaces, workspace plugin controls determine167Review each included app in **Plugins** in Admin console. Where available, use
66which roles can use or install a plugin. The Codex CLI uses its own plugin168**Manage Legacy Apps** to open the older app settings page.
67browser for installation. See
68[Build plugins](https://developers.openai.com/plugins/build/plugins) for
69packaging and distribution.
70 169
71To import workspace plugins from GitHub and keep them up to date, see170- Use **App access** to choose who can use the app.
72[Plugin management](https://learn.chatgpt.com/docs/enterprise/plugin-management).171- Where supported, use **Tools** (or **Actions**) to allow actions that read or
172 change information in the connected service.
173- Use **New tools** (or **New actions**), where supported, to decide whether to
174 allow actions added later. This doesn't turn off actions you've already enabled.
175- Use **Permissions** to choose when ChatGPT asks before using the app.
176
177For example, summarizing documents may need only read actions. Updating project
178records needs write actions. Before allowing write actions, check what they can
179change and how members can review or correct the result. Asking for confirmation
180doesn't replace restrictions on what the app or connected account can access.
181
182If you use a [workspace connection](https://learn.chatgpt.com/docs/enterprise/shared-connections), members
183need permission to use that shared account. Installing a plugin for everyone
184doesn't create a shared account. Choose an account with the permissions the task
185needs, and tell members which account they're using.
186
187Plugins in Sites use each visitor's connected accounts and have a separate
188 Sites permission. See [Plugin access in
189 Sites](https://learn.chatgpt.com/docs/enterprise/sites#enable-plugin-use-in-sites) for defaults and
190 setup.
191
192### Review content access
193
194Some apps offer **Safety & Security Controls** to limit which content ChatGPT can
195access. These settings apply in addition to the connected service's permissions.
196
197For example, a member may be able to open a file in Google Drive while workspace
198content restrictions prevent ChatGPT from accessing it. After choosing
199restrictions, send new requests for an allowed item and a restricted item to
200check that ChatGPT can access the allowed item but not the restricted item.
201
202For supported apps and setup, see the [Help Center's plugin administration guide](https://help.openai.com/en/articles/11509118-admin-controls-security-and-compliance-for-plugins-and-apps).
203
204## Check the member experience
205
206Ask a member to try the plugin in their workspace on a version of ChatGPT or
207Codex that supports it. Test with their account because an owner's account may
208have different permissions.
209
210| Check | What to verify |
211| ------------------------- | --------------------------------------------------------------------------------------- |
212| Find the plugin | The member can install it, or it is already installed, as intended. |
213| Use an included app | The app is enabled, and the correct account is connected with the required permissions. |
214| Try the team's task | The member can use the actions and information the task needs. |
215| Test content restrictions | A new request can access an allowed item and cannot access a restricted item. |
216| Test a write action | If enabled, use a disposable test record. Check the result in the connected service. |
217
218If the plugin is installed but a task fails, check the app connection, allowed
219actions, content restrictions, and the connected account's permissions before
220reinstalling it. For more checks, see [Troubleshooting plugins and apps in ChatGPT](https://help.openai.com/en/articles/20001497-troubleshooting-plugins-and-apps-in-chatgpt).
73 221
74### Troubleshoot "Disabled by admin"222### Troubleshoot "Disabled by admin"
75 223
791. Open [Admin console](https://admin.openai.com), select the workspace, and open **Plugins** (**Apps** in2271. Open [Admin console](https://admin.openai.com), select the workspace, and open **Plugins** (**Apps** in
80 FedRAMP workspaces). Review the plugin's workspace availability and any228 FedRAMP workspaces). Review the plugin's workspace availability and any
81 supported role settings. ChatGPT Business uses workspace-wide availability.229 supported role settings. ChatGPT Business uses workspace-wide availability.
822. If your workspace supports RBAC, review the workspace default and all direct2302. If your workspace supports RBAC, open **Permissions & roles**. Check the
83 and group role assignments in **Permissions & roles**. Confirm the member's231 workspace default and every role assigned to the member, directly or through
84 general plugin permission is enabled: **Allow members to use plugins** or232 a group. The general plugin permission must be on. Look for **Allow members
85 **Use plugins**, depending on the label shown. FedRAMP workspaces may show233 to use plugins** or **Use plugins**. FedRAMP workspaces may show **Use apps**.
86 **Use apps**.
873. Confirm the member can access each app required by the plugin and that the2343. Confirm the member can access each app required by the plugin and that the
88 task's required actions are enabled.235 task's required actions are enabled.
894. Where Lockdown Mode roles are available, check all direct and group role2364. If Lockdown Mode roles are available, check whether they restrict what the
90 assignments for restrictions on the capability the member needs. Lockdown Mode237 member is trying to do. Review roles assigned directly and through groups.
91 doesn't automatically disable every app in managed workspaces, but its238 Lockdown Mode restrictions can apply even when an ordinary role gives access.
92 restrictions can apply even when an ordinary role grants access.239 They don't automatically disable every app in managed workspaces.
93 240
94For self-serve ChatGPT Business accounts, ask the member to review [Lockdown Mode](https://help.openai.com/en/articles/20001061-lockdown-mode) in241For self-serve ChatGPT Business accounts, ask the member to review [Lockdown Mode](https://help.openai.com/en/articles/20001061-lockdown-mode) in
95**Settings > Security**, where available. Lockdown Mode doesn't affect Codex242**Settings > Security**, where available. Lockdown Mode doesn't affect Codex
99security policy. Allow up to five minutes for role changes to apply, then ask the246security policy. Allow up to five minutes for role changes to apply, then ask the
100member to try again. See [Role-based access control (RBAC)](https://help.openai.com/en/articles/11750701-rbac) for details.247member to try again. See [Role-based access control (RBAC)](https://help.openai.com/en/articles/11750701-rbac) for details.
101 248
102### Export the public catalog for review249## Keep approved workflows useful
250
251For each shared plugin, give members a contact who can answer questions and review
252changes to its skills and apps. Review access when the team, task, or connected
253account changes.
254
255When you stop using a plugin, review its installation settings and app access
256separately. Disabling an app doesn't necessarily uninstall the plugin or remove
257skills that work without it. Tell members what's changing and suggest a
258replacement, if one exists.
259
260## Export the public catalog for review
103 261
104Eligible ChatGPT Enterprise workspace owners and admins can download a CSV of262Eligible ChatGPT Enterprise workspace owners and admins can download a CSV of
105the public plugins available to their workspace. Use the export to review263the public plugins available to their workspace. Use the export to review
106plugin, MCP server, and skill metadata before changing plugin availability.264plugin descriptions, apps, and skills before changing availability. Apps use Model
265Context Protocol (MCP) to connect to services, so the export describes them as MCP
266servers. The export doesn't show what each member can access. Use the member
267checks above for that.
107 268
1081. Open [Admin > Plugins](https://chatgpt.com/admin/plugins).2691. Open [Admin console](https://admin.openai.com) and select the intended workspace.
1092. Select **Public**.2702. Open **Plugins** and select **Public**.
1103. Select the download icon (**Export CSV**) in the page header.2713. Select **Export CSV** in the page header.
111 272
112The download uses the filename `public-plugins-security-review.csv` and includes:273The download uses the filename `public-plugins-security-review.csv` and includes:
113 274
116- MCP server metadata: `App Name(s)` and `App Description(s)`.277- MCP server metadata: `App Name(s)` and `App Description(s)`.
117- Chat skill metadata: `Skill Name(s)` and `Skill Description(s)`.278- Chat skill metadata: `Skill Name(s)` and `Skill Description(s)`.
118 279
119When a plugin includes more than one MCP server or skill, semicolons separate the280Semicolons separate multiple MCP servers or skills in the same cell. The catalog
120corresponding values. The export uses a public-catalog snapshot that can be up281data can be up to 48 hours old. It includes public plugins visible to your
121to 48 hours old,282workspace, but not plugins created for that workspace. The export isn't
122includes only public plugins visible to the current workspace, and does not283available in FedRAMP workspaces.
123include plugins created for that workspace. It isn't available in FedRAMP
124workspaces.
125
126## Step 2: Manage capabilities
127
128Conversation sync does not grant additional plugin, MCP server, or connected-service access. For Local computer access with Work Cloud, Agent Security's enterprise `apps` and `plugins` requirements apply to local executors. Work cloud containers retain existing Work Cloud policies. Configure these requirements through TOML and review them alongside workspace permissions and the connected account's permissions.
129
130Review hook support separately from plugin availability:
131
132- **Enterprise hooks.** Where enabled for your workspace, Local computer access with Work Cloud supports admin-defined MCP hooks that run on the cloud coordinator (orchestrator) for supported lifecycle and tool events. Command hooks and hooks from local configuration or plugins are not supported with cloud orchestration, even when tools execute locally.
133- **Cloud orchestration:** Command hooks and hooks from local configuration or plugins do not run, even when tools execute locally and the plugin itself is allowed. Consumers do not have hooks support in this feature. When both orchestration and execution are local, existing supported hooks continue to work in local-only Work and Codex threads. Admins can still configure supported managed hooks in Agent Security for those workflows.
134- **Auditing.** Before relying on these hooks, test the callback connection, confirm the events it receives, and check how failures affect the task. MCP hooks do not provide a complete Compliance API audit trail.
135
136See [Hooks](https://learn.chatgpt.com/docs/hooks) and the [Configuration Reference](https://learn.chatgpt.com/docs/config-file/config-reference) for supported requirements.
137
138<WarningTip>
139 Making an MCP server or plugin available in ChatGPT doesn't grant access to
140 files, records, or actions in the connected service. When troubleshooting
141 access, check the member's workspace role and approved action settings. Then
142 confirm the authenticated account or shared connection has the expected
143 permissions in the connected service.
144</WarningTip>
145
146Plugins in ChatGPT and Codex can include MCP server connections that search, retrieve, sync,
147or act on external systems. Plugin availability and the access and actions
148granted to each connection are separate controls.
149
150Manage MCP server capabilities from
151[Workspace apps](https://chatgpt.com/admin/ca) and
152[Permissions & roles](https://chatgpt.com/admin/settings). Available controls
153let admins:
154
155- Enable MCP server connections and assign access by workspace role.
156- For connections that support **Action control**, allow read-only actions or an
157 approved custom set, including how the workspace handles newly added actions.
158- Set **App permissions** that determine when ChatGPT asks before using a connection.
159- Keep access within the scopes and permissions granted by each connected
160 service and authenticated account.
161
162For current availability and procedures, see
163[Admin controls, security, and compliance in apps](https://help.openai.com/en/articles/11509118).
164 284
165## Restrict company app accounts to authorized workspaces285## Restrict company app accounts to authorized workspaces
166 286
167When activated, verified-domain restrictions prevent users from creating new connections to supported apps with company-domain accounts in personal ChatGPT workspaces or other unauthorized workspaces. Employees must use an authorized workspace to connect those company accounts.287Verified-domain restrictions let you require employees to connect company
288accounts only in authorized ChatGPT workspaces. When activated, this blocks new
289connections to supported apps in personal or other unauthorized workspaces. It
290applies to accounts that use your company's verified domain.
168 291
169Verifying a domain does not activate this restriction. Existing app connections are not automatically disconnected.292Verifying a domain does not activate this restriction. Existing app connections are not automatically disconnected.
170 293
171For supported apps, availability, and setup guidance, see [Admin controls, security, and compliance for plugins and apps](https://help.openai.com/en/articles/11509118).294For supported apps, availability, and setup guidance, see [Admin controls, security, and compliance for plugins and apps](https://help.openai.com/en/articles/11509118).
172 295
173<a id="choose-a-starting-set-of-apps"></a>296<a id="review-runtime-controls-and-hooks"></a>
174 297
175## Choose a focused initial set298## Review permissions for the computer or cloud environment
176 299
177Enable plugins that support an approved business need. Set each plugin’s audience to the users or roles that need it, and complete any required review before enabling it.300If an agent uses plugins on a computer or in a cloud environment, review that
301environment's permissions too. These work alongside workspace and account
302permissions.
178 303
179For each connected service, record the business owner, permitted data, approved304Hooks can run scripts or tools at specific points during an agent's work. If you
180read or write actions, authentication method, and a support or removal contact.305use them, check that the environment supports them and test what happens when
306they fail. A hook failure doesn't necessarily stop the action. Keep access
307restrictions in place even when you use hooks.
181 308
182Before enabling write actions or publishing a new connected capability, verify309See [Agent Security](https://learn.chatgpt.com/docs/enterprise/agent-security) for environment-specific
183its role scope and test with an account that has only the intended permissions310controls and [Hooks](https://learn.chatgpt.com/docs/hooks) for supported events and configuration.
184in the connected service.
185 311
186For a broad rollout, begin with categories teams use every day, such as email,312## Understand data flow and security
187calendar, and file or document systems. Use the
188[Plugins Directory](https://chatgpt.com/apps) to confirm current availability
189and capabilities across supported ChatGPT and Codex surfaces.
190 313
191Whatever the initial set, start with read actions. Before enabling write314When ChatGPT uses an app in a plugin, it sends a request to the connected service.
192actions, identify the plugin owner, review MCP server scopes and service315The account's permissions and workspace controls limit the data ChatGPT can
193permissions, confirm data access, and document external effects and a recovery316access and the actions it can take.
194path.
195 317
196## Understand data flow and security318Before allowing access to sensitive information, review what the task needs,
319which account it uses, and whether the connected service meets your
320organization's requirements.
321
322For current data handling, retention, and compliance guidance, see [Admin controls, security, and compliance for plugins and apps](https://help.openai.com/en/articles/11509118).
323For locally configured MCP servers, see [Codex MCP configuration](https://learn.chatgpt.com/docs/extend/mcp).
324
325<a id="use-current-procedures-and-references"></a>
326
327## Go deeper
197 328
198When ChatGPT uses an MCP server included with a plugin, it sends a request329- [Install and use plugins](https://learn.chatgpt.com/docs/plugins)
199to the connected service and returns data or action results allowed by the330- [Understand skills and plugins](https://learn.chatgpt.com/docs/skills-and-plugins)
200authenticated account's permissions in that service.331- [Import and sync plugins from GitHub](https://learn.chatgpt.com/docs/enterprise/plugin-management)
201 332- Read the [App Security Whitepaper (PDF, June 2026)](https://cdn.openai.com/business-guides-and-resources/app-security-whitepaper.pdf)
202ChatGPT handles data from connected services in two ways:
203
204- **Non-synced:** ChatGPT processes data from Chat and deep research transiently
205 and doesn't index it.
206- **Synced:** ChatGPT indexes selected connected content in advance. You can see
207 whether a connection supports sync on its plugin page.
208
209The mode changes how ChatGPT indexes connected content; it doesn't replace
210normal chat-retention controls. ChatGPT conversations that use these connections remain
211available through the Compliance API.
212
213OpenAI's connected-service guidance documents encryption in transit and at rest, per-user
214authorization, role and action controls, restricted network access for
215conversations that use these connections, and no model training on information accessed
216through these connections for Business, Enterprise, and Edu customers. When a request reaches
217a connected service, that service's scopes, retention, data residency, and other
218policies also apply.
219
220See [security and compliance for connected services](https://help.openai.com/en/articles/11509118)
221and [connections with sync](https://help.openai.com/en/articles/10847137) for current
222data-handling details. For locally configured MCP servers in the ChatGPT desktop
223app, Codex CLI, or IDE extension, see
224[Codex MCP configuration](https://learn.chatgpt.com/docs/extend/mcp).
225
226## Use current procedures and references
227
228- [Admin controls, security, and compliance in apps](https://help.openai.com/en/articles/11509118)
229- [Apps in ChatGPT](https://help.openai.com/en/articles/11487775)
230- [Apps with sync](https://help.openai.com/en/articles/10847137)
231- [Manage workspace settings](https://help.openai.com/en/articles/8411955)
232- [Plugins](https://learn.chatgpt.com/docs/plugins)
233- [Skills and plugins](https://learn.chatgpt.com/docs/skills-and-plugins)
234- [Build plugins](https://developers.openai.com/plugins/build/plugins)
235- [Admin rollout guide](https://learn.chatgpt.com/docs/enterprise/admin-setup)
