Common Errors

If something you expected to work returns an error, the cause is almost always one of these three: you are not signed in, you do not belong to an organization, or you do not have the right role on the resource.

“You need to join an organization before creating resources”

You are signed in, but the server doesn’t see any organizations on your account. Creating a project requires an owning organization, so the request is rejected.

What to do: Ask your identity provider administrator to add you to the appropriate group or team. The next time you sign in, your organization membership will sync automatically and you can retry.

“Permission denied” or HTTP 403

You reached the server with a valid session, but the resource refuses you. The two most common reasons:

• The resource is Restricted and you are not the owner, not explicitly invited, and your organization has not been granted access. Ask the owner to share it with you or your organization.
• You have Viewer access on a resource you tried to modify. Reading is allowed; writing is not. Ask the owner to upgrade you to Editor if you need to make changes.

If neither applies, check whether the access mode of the resource has been changed recently — it may have been switched from Organization to Restricted.

“Not authenticated” or HTTP 401

Your session has expired or you never signed in. Sign in again and retry.

For Anonymous resources you should never see this error; if you do, the resource has likely been switched out of Anonymous mode.

Managing Access as an Owner

Right now, changing access modes and granting access to other users or organizations is performed via internal admin endpoints maintained by FSL. A self-serve UI for resource owners is on the roadmap.

If you need to change access on a resource you own, contact your FSL representative.