Skip to main content

πŸ” Roles and permissions

This page explains who can do what in the CMS for campaigns. It also covers optional approvals and audit trails.

Leo avatar
Written by Leo
Updated over 5 months ago

Roles at a glance

  • Admin
    Full control inside your organisation. Creates and manages campaigns, devices, locations, members, and settings.

  • Manager
    Day-to-day operator. Creates and manages campaigns and devices. No access to organisation user management.

  • Viewer
    Read only. Can browse campaigns, versions, previews, analytics, and device status.

  • Author (experience developer)
    Builds Experiences and Experience Releases. Can see release code metadata such as GitHub repo and branch. Client organisations cannot see these details.

Campaign permissions matrix

Capability

Admin

Manager

Viewer

Author

View campaigns and versions

βœ…

βœ…

βœ…

βž–

Create campaign

βœ…

βœ…

❌

βž–

Edit campaign content

βœ…

βœ…

❌

βž–

Validate and resolve required fields

βœ…

βœ…

❌

βž–

Duplicate a campaign

βœ…

βœ…

❌

βž–

Schedule start date and targets

βœ…

βœ…

❌

βž–

Publish a campaign

βœ…

βœ…

❌

βž–

Archive or restore

βœ…

βœ…

❌

βž–

Share preview links

βœ…

βœ…

βœ…

βž–

View change log and diffs

βœ…

βœ…

βœ…

βž–

Export data and reports

βœ…

βœ…

βœ…

βž–

Manage devices and device actions

βœ…

βœ…

❌

βž–

Manage locations and translation preferences

βœ…

βœ…

❌

βž–

Manage organisation members and roles

βœ…

❌

❌

❌

Create Experiences and Releases

❌

❌

❌

βœ…

View Git repo and branch on releases

❌

❌

❌

βœ…

Legend: βœ… allowed β€’ ❌ not allowed β€’ βž– not applicable

Approvals

  • Standard: No approval workflow is required to publish.

  • Enterprise option: A multi step approval flow is available on request. You can require specific reviewers before publish. Contact support to enable.

Notifications

  • By default Admins and Managers receive dashboard notifications for schedule created, publish, failure, and rollback events.

  • Viewers can see the status in the UI but do not receive action notifications.

Audit trail

  • The CMS records who changed what and when, including content edits, target changes, schedule edits, publishes, and restores.

  • Admins and Managers can view the audit log. Viewers have read access to version history and diffs.

Security notes

  • Experience release source code links are visible to Authors only. Client organisations cannot see repo or branch details.

  • Use role scoping to limit risk in production. Grant Manager where possible and reserve Admin for a small set of owners.

Did this answer your question?