We’re planning to retire custom GPTs and help creators move their workflows to plugins. Plugins bring reusable instructions, reference files, and connected apps together.
For affected Enterprise workspaces, new GPT creation ended on October 26, 2026. FedRAMP workspaces are excluded from this creation cutoff and can still create GPTs. Existing unmigrated GPTs remain usable and editable until their applicable retirement date. After migration, the original GPT becomes read-only. Standard retirement is scheduled for December 11, 2026. FedRAMP workspaces and workspaces with a qualifying, approved deferral have a retirement date of February 11, 2027.
The transition includes all ChatGPT plans, but creation restrictions and migration access depend on the account or workspace. Follow the notice for yours. For dates, migration steps, and what to expect on other plans, see: Custom GPT retirement and migration FAQ.
Overview
This article explains how GPT-related workspace controls affect building, sharing, access, and governance in Enterprise and Edu workspaces. It is intended for workspace owners and admins who manage GPT access for their organization.
Availability
Availability for GPT features varies by plan and workspace permissions. For general availability details, see: GPTs in ChatGPT.
New GPT creation ended on October 26, 2026 for affected Enterprise workspaces, with the exception of FedRAMP workspaces. Existing unmigrated GPTs remain usable and editable until their applicable retirement date. After migration, the original GPT becomes read-only. For dates and migration guidance, see: Custom GPT retirement and migration FAQ.
Workspace roles do not override product availability. For individual migration, a GPT’s creator or a workspace admin can migrate it when the required access is enabled. Retrieving the full inventory for bulk migration currently requires a workspace Owner.
Permissions and roles (RBAC)
The following can be configured in Workspace settings > Permissions & roles. You may set them at the workspace level or assign them through custom roles:
Who can create or edit GPTs through workspace settings and role permissions.
Whether GPTs can be shared, and whether sharing is limited to invite-only, workspace-only, or broader sharing levels.
Whether users can access third-party GPTs, only owner-approved third-party GPTs, or no third-party GPTs.
For more on configuring workspace permissions and custom roles, see: Role Based Access Controls for ChatGPT Enterprise.
Workspace-level controls
The following can be configured in Workspace settings > GPTs. They are applied at the workspace level and cannot be customized for individual roles at this time.
Apps
Workspace admins can control whether apps can be used in GPTs created in the workspace. If apps are disabled, GPTs created in your workspace cannot use apps. This setting does not apply to third-party GPTs.
Actions
Workspace owners can also restrict GPT actions to specific allowed domains for GPTs created in the workspace. If no domains are added, GPT actions are not allowed. Allowing a parent domain also allows its subdomains.
If a GPT uses actions that do not comply with workspace domain restrictions, those actions may be rejected or unavailable until they are updated or removed.
For instructions on configuring apps or actions in a GPT, see: Creating and editing GPTs and Configuring actions in GPTs.
Collaboration and ownership
In managed workspaces, GPTs can support collaboration through sharing permissions. Depending on the permission level assigned, collaborators may be able to:
Use a GPT with Can chat.
View its configuration with Can view settings.
Update it with Can edit.
GPTs also have an owner. Some workspace-level GPT management actions, including ownership changes and certain workspace approval actions, are restricted to workspace owners.
For steps to share a GPT and assign permissions, see: Sharing and publishing GPTs.
Ownership continuity
If the owner of a GPT is deactivated or removed from a managed workspace through the normal workspace removal flow, the GPT is not left without an owner. Ownership is transferred to a workspace owner, and the GPT is marked as unassigned so workspace owners can review or reassign it if needed.
If the original creator is later re-added to the workspace, ownership can be restored automatically to that person. Workspace owners can also manually reassign GPT ownership to another workspace member at any time.
SCIM-managed group sharing
Where available, workspace owners can use Discoverable by workspace users to control whether SCIM-managed groups appear when people share GPTs or projects. This setting does not grant access to the workspace’s full group list. If the workspace’s identity settings are read-only and the control is unavailable, ask your OpenAI account team about supported options.
For setup and group-management guidance, see: SCIM provisioning and management.
Compliance
Conversations with GPTs are available in the Compliance Platform. For technical details, see: Conversation Messages API reference.
Reporting
Workspace analytics includes a GPTs section where eligible viewers can track GPT adoption and other metrics.
For more on available metrics and information on workspace analytics, see: Workspace Analytics in ChatGPT Enterprise and Edu.