I have a pre-existing custom connector (MCP server with search and fetch) that is now an “app” that had been published to the business workspace and working consistently for months. After the migration to “Apps” no workspace users can see or access it except for the admin that published it to the workspace who sees it under enabled. Even if I delete and recreate it, re publish/enable etc only that original admin can ever see and use it (it works)i I suspect there are some wires crossed with the Apps permission. It should show in the directory for other workspace users after publishing I would assume. Another admin can see it in the directory, but it is not enabled, and if they try to enable it there is an error “only an admin can enable” (despite them being an admin) and my admin account having already published it and consented to the form).
I’m facing the same issue. As an admin, I’ve published the connector, but it is completely invisible to others in the following locations:
-
Settings > Enabled apps / Drafts
-
The App Directory (chatgpt.com/apps)
The only workaround I found (for Admins only) is:
-
Go to the Admin Console (chatgpt.com/admin/ca).
-
Select the specific connector.
-
Click the ‘Show in directory’ link and then click ‘Connect’.
This allows other Admins to add and use the custom MCP connector. However, this is not a solution for regular Members, as they don’t have access to the Admin Console. There is currently no way for regular workspace members to find or use the published connector.
I’m seeing the same behavior in my workspace (Business plan). When I publish a custom connector as an admin, it does not show up in the Apps/Connectors directory for regular members, so they can’t find it there.
However, what does work as a temporary workaround is this:
-
As the admin, I go to the Apps → my custom conntettor, then open Details > Show in directory.
-
A new page opens where the connector can be connected, and I share that link with the other team members.
-
When they open that link and connect/authorize the connector, it then becomes available in their workspace and shows up among their options.
Once they have connected it via that direct link, they can use it like any other app/connector without issues.
This is obviously just a workaround, not a real fix. Hopefully OpenAI addresses this soon, because the current behavior makes it difficult for teams to properly discover and adopt admin‑published custom connectors.
@casey-chow hi 
An update in the last week has broken this for us as well. During a client demo, we identified a critical bug that prevents users on our Business/Enterprise account from accessing and enabling custom internal GPT apps published for the workspace. The issue stems from the App Directory no longer displaying workspace-specific applications via the intended flow.
Issue Description:
On Business and Enterprise plans, the designated Workspace Specific tab in the App Directory is missing. This prevents users from independently finding and connecting internal apps to their chat window, despite the apps being enabled for the workspace by an administrator.
When a non-admin user attempts to access the App Directory via Settings → Apps → Add more, they are shown the directory window containing only public categories (Featured, Lifestyle, Productivity). The absence of the “Workspace” tab means no internal, published apps are visible.
Since all roads lead back to this disabled path 404 Page, the user is unable to click the necessary Connect button to add the app to their personal workspace. Because the app’s connection page cannot be found, and the user is blocked from adding the internal app to their chat. Even though it is visible in the “Enabled” tab in the workspace app setting.
Steps to Duplicate:
Log in as a non-owner/non-Admin Member on a Business or Enterprise account.
Go to Settings (gear icon) → Apps → Add more.
Observe that the App Directory window opens but is missing the expected Workspace Specific tab that should display internal applications.
Confirm that no custom, published internal apps are visible or discoverable in this directory.
The inability to access the app’s listing page prevents the user from clicking Connect, thereby ensuring the app is not added to their user chat.
Current Workaround:
We have identified a temporary and cumbersome workaround that requires the Workspace Owner to manually elevate and demote each user who needs access:
The Workspace Owner must temporarily promote the user to an Admin role.
The newly promoted Admin gains access to the Advanced Settings button/Developer mode.
The user must then publish the required app for themselves and ensure they click Connect to add the app to their personal account.
Once the app is connected and functioning, the Owner would then demote the user back to a Member role.
The app remains connected and functional in the user’s chat even after the user is demoted, and developer mode is automatically turned off.
Please prioritize restoring the App Directory display issue to eliminate this cumbersome workflow that requires temporary elevation of user privileges and proliferation of duplicate apps in the workspace.
We’ve got the same issue as @VibeandGrind with the same symptoms and workaround.
It actually was working this morning for us, but after I deleted and re-created an app, all the custom apps disappeared from the directory, and newly created ones haven’t shown up either.
Looking forward to this being fixed!
Having the same problem as @VibeandGrind and @maxcutlyp
Having the same problem here on the business plan. Our internal workspace app is no longer showing up in our app directory and also doesn’t appear in search results after re-creating and publishing it, so none of our internal users are able to access the app anymore. Some resolution would be much appreciated.
same issue as @Piet01 and others. it’s a blocker for our work at the moment.
Same issue as described by other users/developers. This is blocking our current workflows.
@OpenAI_Support any update on this?
Same issue we are also facing
We are also having this issue and it is having a big impact on team productivity our internal app is the main tool we use in our business workspace. This seems like a regression this issue occurred a few months ago please resolve it! Big difference this time even trying to go to the direct url gives a 404 in addition to the app no longer showing for users in the directory.
Exact same issue as described by VibeandGrind in message 4 of this thread. Any update would be great!