Roles & Permissions

SitePulse uses four organization roles: Owner, Admin, Member, and Viewer. Roles are per-organization — you can be an Admin in one org and a Member in another.

Role capabilities

Owner

There must always be at least one Owner per organization. The Owner role cannot be removed if they are the last owner — another member must be promoted to Owner first.

Owners are the only role with access to billing and subscription management.

Admin

Admins can do everything except access billing or delete the organization. Use the Admin role for team leads or account managers who need full operational access without financial controls.

Member

Members can run audits, review rewrites, and work with personas and brand voice, but cannot make changes that affect the organization configuration. Use the Member role for individual contributors who do day-to-day work.

Viewer

Viewers see everything and change nothing: they can browse projects, audit reports, trends, and AI Visibility results, but every action that changes data — running audits or AI Visibility checks, editing questions, applying fixes, changing brand voice — is blocked. Use the Viewer role for clients and stakeholders who should follow progress without being able to (accidentally) spend your audit quota or alter configuration.

Changing roles

Owners and Admins can change any member's role via Settings → Team → Members. Click the role badge next to a member's name and select the new role.

An Owner can demote themselves to Admin, but only if another Owner exists. SitePulse enforces the single-owner constraint — downgrading the last owner is blocked.

Impersonation (platform support only)

Impersonation — viewing the app as another organization — is a SitePulse platform-support capability, not an organization role. It is read-only by design: a support engineer impersonating your organization can see what you see but cannot change anything. See Impersonation for details.