Restricted workspaces
A restricted workspace shows a banner at the top of the dashboard and blocks publishing, previews, actions, new apps, and more. The fix always runs through support: use the Contact support link in the banner or email [email protected].
The banner reads: "This workspace has been restricted and cannot publish, share previews, run actions, or create new apps."
Recognize the restriction
Every member of the workspace sees the restriction banner, not only owners and administrators. Alongside the banner, many controls are hidden or disabled: creating new apps, uploading files, publishing, sharing previews, running actions, and creating an additional workspace.
What is unavailable
While the workspace is restricted, the following actions are blocked or their controls are hidden:
Creating new apps, including Sites, Embeds, and Documents, plus Start from template and Duplicate document
Uploading files and assets
Publishing
Sharing previews
Running actions, including conversion actions
Creating an additional workspace: Add new workspace is hidden from the workspace picker
The built-in AI assistant
Connecting the Meta, Stripe, Google Ads, HubSpot, and Google integrations, generating new API keys, and retrying a failed conversion delivery
Adding a custom domain: the Domain field, Add domain, and Verify domain are disabled on the Domain settings page
Inviting members: Add new member and Send Invite are hidden, and sending or accepting invitations is blocked
Stripe charge execution for payments
Previews and publishing
Preview access is unavailable while the workspace is restricted. Direct preview requests and preview PIN submissions return "Preview unavailable." On the site and Embed share pages, preview PIN and URL sharing is removed.
Publishing is blocked. The editor shows: "This workspace is currently not approved to publish. Contact support if you believe this is an error." For how publishing normally works, see Preview and publish your website.
Files and downloads
New file uploads are blocked for the workspace. Files owned by a restricted workspace can only be downloaded by members of that workspace, including files that would otherwise be publicly downloadable.
API-key access
Requests authenticated with a workspace API key fail while the workspace is restricted. The API returns HTTP 403 with the error {"error": "workspace is restricted"}. This applies to Zapier and MCP requests as well. Existing API keys in Connect integrations cannot be replaced, because generating new keys is blocked.
What still works
You can still open the restricted workspace and switch between your workspaces from the workspace picker. Existing members remain visible in the Members settings.
Contact support
If you believe the restriction is an error, click Contact support in the banner or email [email protected]. We can review the restriction.
Related articles: Manage workspace members, Connect a custom domain, and Convert Zapier API.