Troubleshoot access problems
On this page
When the Users view refuses a change, it explains why in one sentence. Match the message below to its fix.
- Check that you selected the right app, Preview or Production.
- Find the message in the table and follow the fix.
- Repeat the change. If the message stays, note the exact sentence for support.
| Message | Fix |
|---|---|
| An organization must keep at least one owner. Make someone else an owner first. | Switch Owner on for another member, then change the first one. |
| Only an owner of the organization can do this. | Ask an owner of that organization, or sign in as one. |
| This person already belongs to the maximum number of organizations. | Remove them from an organization they no longer need. |
| This organization no longer exists or has nobody in this app. | Reload the Organizations tab and choose another. |
| This person is not a member of the organization. | Add them as a member first. |
| This member was added by the platform for your own team and cannot be changed here. | Leave the Managed member as is, or restrict their permissions. |
| This is the person’s own organization, so they cannot be removed from it. | Keep them in it. To end their access, remove them from the app in the Users tab. |
| This app keeps everyone in one organization; organizations of their own are turned off for it. | This app was created without organizations of its own. See Build for multiple customer organizations. |
| The members, bundles and existence of this group are kept by the platform and cannot be changed. | Change the group’s permissions instead. |
| This default does not fit the permission. | Choose a class the permission allows. See Set default permissions. |
| A permission can be bound to organizations only in an area the app’s organizations are turned on for. | Leave it unbound. Organization-bound permissions need organizations turned on for that area. |
| Someone still holds this permission in an organization. Revoke those grants before unbinding it. | Revoke the grants, then unbind. |
| Choose the organization this permission is granted in. | Pick an Organization in the person’s Permissions dialog. |
| This permission belongs to the platform and cannot be changed here. | Use another permission. |
Sign-in and access-denied problems
- A visitor sees “Sign in to continue”: they are signed out. Ask them to sign in again.
- A signed-in person sees the access-denied view: grant the permission or add them to a group that has it.
- No code arrives: check the address, wait a minute and request again. Addresses ending in
.testnever receive email. - Someone who should have access is missing: check the other app, Preview or Production.
The MCP reference covers the same operations for agents. Back to the section overview.
Application example
Category: Project and task management. Example: Task Grove, a task board for a small team. A manager cannot be demoted until another owner exists, so make a second owner first.