@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.