Skip to main content

​
Can’t access a workspace

Your Roblox role almost certainly does not have panel access. Panel access defaults to off for every role, so this is the usual cause rather than anything being broken. An owner can enable it under Configuration → Roles & Permissions.
Confirm you are in the correct Roblox group with the rank you expect. Access is evaluated when the session is created, so if you were promoted while signed in, sign out and back in.

​
Roblox sign-in fails or the redirect breaks

The redirect URI registered on the Roblox OAuth application has to match the one Crovant sends, exactly. If the site has moved — a new domain, or a change in where the API is served from — the registered URI can be left pointing at the old address, and Roblox rejects the redirect before Crovant ever sees it.
Both /api/roblox-oauth-callback and the legacy /.netlify/functions/roblox-oauth-callback resolve to the same handler, so either can be registered — but the one registered at Roblox must be the one being sent.

​
Missing portal data

Refresh to reload workspace data, then confirm the content exists for this workspace — events and posts belong to one workspace and do not appear in another.
The Discord bot is currently disabled, so this is expected for now — posts publish in Crovant and go no further.When it is running, a post publishing in Crovant still does not mean Discord accepted it. Re-verify the integration; a bad webhook fails without surfacing an error.

​
API errors

Most endpoints are workspace-scoped. Pass ?workspaceId=....
Check the API key from Configuration → API, and that it is sent as Authorization: Bearer <key> — not as a query parameter.
The reason in the response body says which check failed:Also confirm the workspace is active and not archived, and that your plan covers the endpoint.
Usage is attributed to the workspace in the request, not the key’s owner. A key used across workspaces bills each separately — check Configuration → API for the workspace in question.