Team Member roles explained
What each Team Member role can do — Owner, Admin, Manager, Developer, Editor, Author, and Viewer — so you can assign the least-privileged role that fits.
Every Team Member has a role that controls what they can do in your workspace. Acrosite offers seven roles, from full control to read-only. This reference explains each one so you can assign the least-privileged role that lets someone do their job.
Who this is for
Workspace Owners and Admins, who assign and change Team Member roles.
The roles
When you invite a Team Member or change their role, you choose from:
- Owner — full control of the workspace, including billing. There is one protected Owner per workspace; this role is not assigned from the invite flow.
- Admin — manages the team, projects, and integrations, and can invite and manage other Team Members.
- Manager — manages reviews, scheduling, and publishing for content.
- Developer — manages GitHub Setup and Deployment Setup for projects.
- Editor — creates and edits content, fills in Custom Fields, and manages media.
- Author — creates and edits content and submits it for review.
- Viewer — read-only access.
Choosing a role
Pick the lowest-privileged role that still lets the person do their work. An editor who only writes does not need Admin; a developer who only sets up deploys does not need to manage the team. You can change a role later from the Team page, so it is safe to start narrow.
Roles and your plan
Team Members (and pending invitations) count toward your plan's Team Member limit. If you reach the limit, the invite action is unavailable until you upgrade or remove a member. See Billing, trial, and plan limits.