Migrated GPT is private in ChatGPT Business, and plugin sharing is disabled for the workspace owner

GPT builders Plugins / Actions builders
, , , ,
1

I’m the owner of a ChatGPT Business workspace. We use several custom GPTs to run internal workflows. I migrated HRgpt, an HR policy assistant our employees use, after seeing the retirement notice. The migration reported success, but the replacement plugin is Private and I cannot share it with the team.

On the plugin detail page, “Share plugin” is disabled with this message: “Plugin sharing isn’t enabled for your role or workspace.” I’m the workspace owner, and I cannot find the Share plugins or Publish plugins to workspace controls that the documentation and support assistant direct me to enable. The plugin record shows scope: WORKSPACE and discoverability: PRIVATE.

An employee opening the plugin link gets “Try again later.” This has taken an internal policy tool out of use. The migration flow indicated I could change visibility afterward, but the control to do that is unavailable.

I’ve provided the plugin IDs, error text, and reproduction details to OpenAI Support. The case has been escalated, and I’m awaiting a response. Has anyone with a Business workspace encountered this and found a working solution? Is plugin sharing currently supported for Business workspace owners, or is this a rollout or entitlement issue?

2

Got to love this - they put the please migrate before Dec 11th and then they don’t actually enable the sharing feature.

Hello,

Thank you for reaching out to OpenAI Support, and we hope this message finds you well.

We understand the impact here. HRgpt has already been communicated to your employees as the way to access company vacation, attendance, leave, and related HR policy information, but employees currently cannot access it because the migrated plugin remains Private. We also understand that you have already spent significant time checking the sharing controls previously suggested.

Our current plugin guidance confirms that new workspace plugins start private. When plugin-sharing permissions are available, workspace administrators can review them under:

Workspace settings → Permissions & roles → [role]

The relevant permissions can include Use plugins, Share plugins, and Publish plugins to workspace. After sharing is enabled, a plugin owner can normally open Plugins → [plugin] → ••• → Share plugin and select an available access option, such as Anyone in this workspace with the link or Visible in workspace directory. Pasted markdown

However, the documentation also notes that these controls are available where available, and plugin availability can depend on the account, workspace, role, region, rollout, and included capabilities.

Best,

Florentino

OpenAI Support

My reply:

Please escalate this as a workspace entitlement or product defect, rather than sending sharing instructions again. In the Puget Sound Instrument workspace, migrated HRgpt (plugin_3db64cab733081918d02a56a72996899) is Private, the admin Share plugin button is disabled, and Permissions & roles exposes no plugin-sharing permission. Employees cannot access the HR policy tool we already announced. Is direct sharing of migrated plugins supported for our workspace today? If yes, please identify and fix the specific blocker. If no, please provide the rollout date or a supported interim way to make HRgpt available to employees in ChatGPT web and mobile.

3

Update and correction: I rechecked HRgpt. The original GPT is still shared with our workspace (“Can chat”), and ChatGPT says it can be used until December 11, 2026, although migration made it read-only. My earlier statement that the HR tool was entirely unavailable was too broad. The failure is the replacement plugin: it remains Private, “Share plugin” is disabled for me as the Business workspace owner, and an employee opening its link received “Try again later.”

OpenAI’s updated migration FAQ now explicitly says sharing settings do not transfer and existing users do not automatically gain access to the replacement. The plugin guidance describes sharing permissions “where available.” Those controls still do not appear in our Business workspace.

As a stopgap, I used Codex to recreate HRgpt as a temporary custom GPT with its reference files and policy rules. I tested sample questions and shared it with the workspace; access from an employee account still needs verification. This does not fix plugin sharing, and custom GPTs are scheduled to retire December 11.

Migrate at your own risk until OpenAI gets sharing under control. Record who can use your GPT and have a regular user test the replacement before directing anyone to it. OpenAI, please clarify when Business owners will receive the missing sharing controls and how to make already-migrated private plugins accessible.

4

There’s a bunch of threads around the custom GPT to Plugin. First, the plugin during the wizard is a lazy go at it, not as efficient as if you redo it.

You can download the migrated/generated plugin as a zip, then re-upload the zip toa chst gpt session and have it walk you through splitting the instructions/crating skill folders.

Once it’s all done you zip it back up and upload ot, that version will be shareable with your team right away.

5

I’ve created brand new plugins from scratch using CODEX.

The privacy settings are stuck on private and at least for my workspace the share button is completely grayed out.

The documentation says all plugins are set to private and that publishing depends on rollout timing.

I recreated the migrated HR gpt plugin as a new temporary one for using a similiar method to yours. Nothing I’ve done allowed the private setting to be changed.

I did the HR one first because of it was all .md files and fairly simple.