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
GPT sharing and publishing options depend on your account and workspace settings.
Personal ChatGPT accounts, including Free, Go, Plus, and Pro, cannot create or publish new GPTs. Existing GPTs remain usable and can still be edited if existing plan and permission requirements are met.
In managed workspaces, GPT creation, sharing, and publishing depend on product availability, workspace settings, and permissions.
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.
Availability
Personal ChatGPT accounts cannot create or publish new GPTs. Existing GPTs remain usable and can still be edited if existing plan and permission requirements are met.
In managed workspaces, GPT creation, sharing, and publishing depend on workspace settings and role permissions.
For plan eligibility, see: GPTs in ChatGPT.
Check your workspace notice and the options available for the existing GPT. New GPT creation ended on October 26, 2026 for affected Enterprise workspaces, with the exception of FedRAMP workspaces. Public sharing is not required. Migration uses the latest published version; drafts and unpublished edits do not transfer.
Share a GPT
If a sharing option is available for a GPT, open it in the editor and select Share.
In managed workspaces, a GPT must be created before it can be shared. Personal ChatGPT accounts cannot create or publish new GPTs.
Open the GPT in the editor.
Select Share.
Choose a sharing level.
Choose a permission level.
Select Save to apply sharing changes.
Copy the GPT link if you want to send it directly.
If you share a GPT directly with a user, they will receive an email notification with a link to the GPT.
Sharing levels
Invite-only: Keeps access limited. For personal accounts, this means only you. In managed workspaces, it can also include specific users or groups you add.
Anyone at your workspace with the link: Anyone in your workspace who has the link can access the GPT.
Your workspace: Anyone in your workspace can access the GPT.
Anyone with the link: Anyone who has the link can access the GPT, if public link sharing is available to you.
GPT Store: Eligible GPTs can be published publicly when account eligibility, workspace settings, and permissions allow it. Personal ChatGPT accounts cannot publish new GPTs.
Personal ChatGPT accounts cannot create or publish new GPTs. Existing GPTs remain usable and can still be edited if existing plan and permission requirements are met. Available sharing options depend on the options shown for the account.
Permission levels
Can chat: Users can use and chat with the GPT.
Can view settings: Users can use the GPT and view its configuration settings. Duplicating it also requires eligibility to create new GPTs.
Can edit: Users can make direct changes to the GPT.
Some sharing levels support only Can chat. For example, public link sharing and GPT Store publishing do not support Can view settings.
Share within a workspace
In managed workspaces, you can share a GPT either with specific users or groups or more broadly across your workspace. Workspace admins can limit or disable some sharing options. For more information, see: Managing GPT access in Enterprise and Edu workspaces.
Sharing limitations
Direct sharing with specific users or groups is available only in managed workspaces.
You can share a GPT directly with up to 100 recipients, including individual users and groups. Each user or group counts as one recipient, regardless of how many users are in the group.
For example, you could share a GPT with 50 individual users and 50 groups, even if those groups contain many members.
This limit applies only to direct sharing with specific users and groups. It does not apply to broader workspace sharing options.
Publish to the GPT Store
Publishing to the GPT Store makes your GPT publicly available through ChatGPT.
When you publish to the GPT Store, you may be asked to:
Choose a category.
Review how your builder name or website appears.
Confirm that the GPT meets applicable policy and product requirements.
Eligibility and constraints
Publishing to the GPT Store depends on your plan and, in managed workspaces, your workspace settings and role permissions.
Publishing to the GPT Store depends on your plan and, in managed workspaces, your workspace settings and role permissions.
A GPT may not be eligible for public publishing if:
Public publishing is disabled for your workspace.
The GPT uses app connections that are not supported for the sharing or publishing option you selected. If you see an app-related blocker, remove the affected app connection and try publishing again.
The GPT uses actions without a valid Privacy Policy URL.
The GPT is restricted by sharing or policy checks.
Your workspace or account is subject to restrictions that prevent marketplace publishing.
Builder profile
To publish a GPT to everyone, you may need to complete your builder profile.
Your builder profile can include:
Your name
A website link from a verified domain
Supported verified social profiles
For personal accounts, verification can involve billing details or verifying ownership of a public domain name. In managed workspaces, you may need your workspace administrator to set up or approve builder profile details.
Only verified domains can be used for the public website link shown in your builder profile.
Actions and policy requirements
If your GPT uses actions and you want to share it publicly or publish it to the GPT Store, each public action must include a valid Privacy Policy URL.
Public GPTs must also meet OpenAI policy and product requirements. If a public sharing option is unavailable, the GPT may need changes before it can be shared more broadly.
Review and publishing
Before a GPT can be shared more broadly or published to the GPT Store, it may be checked automatically against sharing and policy requirements.
If publishing is blocked, you can:
Update the GPT and try again.
Appeal the decision, if an appeal option is available.
Keep the GPT private and continue using it yourself.
After publishing
You can continue editing an existing unmigrated GPT if your plan and permissions allow it. After migration, the source GPT becomes read-only; make further changes to the replacement plugin.
Changes save to a draft while you edit.
Select Update to apply draft changes to the live GPT.
Use Share to change who can access the live GPT.
A published GPT’s public surface may include its name, icon, description, category, capabilities, conversation starters, ratings if available, and builder profile details.
Appeals and restrictions
If a share or publish action is blocked and an appeal option is available, you can submit an appeal with additional context.
While an appeal is under review:
You can continue using the GPT privately.
You cannot edit or update it.
You cannot share it with others until the appeal is resolved or you cancel it.