Permission errors
When Acrosite says you do not have permission for an action, your role decides what you can do. Here is how to tell what is happening and what to do next.
When Acrosite tells you that you do not have permission for an action, it is enforcing your role. Access depends on your role, your scope, and the resource — not a single switch. This guide explains what to do.
Why it happens
Acrosite checks permissions on the server for every protected action. If your role does not include an action — for example, an Author trying to approve content, or a Viewer trying to edit — Acrosite blocks it. See Roles reference.
What to check
- Your role. Open the workspace Team page (or ask an Owner or Admin) to see your role. Different roles can do different things — see Team Member roles explained.
- The action. Some actions are role-gated: approving and requesting changes are for Owners, Admins, and Managers; GitHub and deployment setup are for Developers (and Owners/Admins); billing is for the Owner.
- The resource. Make sure you are acting on something in your own workspace and within your scope.
How to get the access you need
If you need to do something your role does not allow, ask an Owner or Admin to either change your role or perform the action. Roles are changed from the Team page. See Manage Team Members.