Team roles — owner, editor, viewer

The three roles

Avago keeps access control simple with three roles. Each person you invite to a site gets exactly one, and it sets what they can do:

• Owner — full control, including billing, publishing, settings and inviting others.
• Editor — can build and edit the site, but can't touch billing or the most sensitive settings.
• Viewer — can see the site and leave comments, but can't make changes.

The idea is least privilege: give each person the lowest role that lets them do their job.

The capability matrix

Who can do what, at a glance:

• Edit content and design — Owner, Editor.
• Add and arrange pages and sections — Owner, Editor.
• Publish and unpublish — Owner (and Editor where granted).
• Manage billing and plan — Owner only.
• Connect domains and integrations — Owner.
• Invite and manage people — Owner.
• View and comment — all roles, including Viewer.

When in doubt, an Editor can shape the site; only an Owner can change what it costs or who else gets in.

Custom roles

The three standard roles cover most teams cleanly. Where an agency or larger team needs finer control — for example separating who can publish from who can only draft — that's handled in the agency workspace, where access can be arranged around your particular workflow.

Hand clients a Viewer role when you want them to review and comment without risk of an accidental edit, and promote them to Editor only if they genuinely need to change content themselves.