Roles and Permissions
The Content Builder uses a level-based role system to control which features and actions are available to each user.
Each role includes the permissions of all lower levels. This means that users with a higher role level can also perform all actions available to users with lower role levels.
Which role are you currently assigned to?
- Click on the Menu on the upper right corner (where "Track and Communicate" or "Online Return Center" is displayed)
- Check the role in the very bottom info
Permission Overview
The following table provides a comparison of the permissions available for each role.
| Capability | Viewer | Contributor | Expert | Admin |
|---|---|---|---|---|
| View available releases | ||||
| Preview release content | ||||
| Send test emails | ||||
| Export content to Excel | ||||
| Import content from Excel | ||||
| Edit content in the frontend | ||||
| Approve and publish releases | ||||
| Edit templates | ||||
| Create templates and content elements | ||||
| Configure modules and events | ||||
| Edit demo payloads | ||||
| Copy content between stages | ||||
| Manage users | ||||
| Assign user roles |
Info
Permissions are inherited. Each role automatically includes all permissions assigned to the lower role levels.
What can each role do?
Where to use this role?
The Viewer role is the default role. No changes can be made with this role.
Typical users
Potentially any client-side MyArvato user.
Permissions
- View all available releases
- Preview release content
- Send test emails for all available releases
Restrictions
- Cannot edit content
- Cannot approve or publish releases
- Cannot edit templates
- Cannot change configurations
Where to use this role?
Assign the Contributor role to users who are responsible for maintaining and publishing content.
Typical users
Client content editors and members of the Arvato client team.
Includes all Viewer permissions, plus:
- Edit content in the Content Builder frontend
- Export content to Excel
- Import content from Excel
- Approve and publish releases
Restrictions
- Cannot edit templates
- Cannot configure modules
- Cannot manage users or role assignments
Where to use this role?
Expert users have access to advanced functionality. Changes should only be made by users with the required technical knowledge.
Typical users
Frontend developers, content experts, UX specialists, and client agencies.
Includes all Viewer and Contributor permissions, plus:
- Edit existing templates
- Create new templates
- Create new content elements
- Access advanced Content Builder functionality
- Make extended changes within the assigned environment
Restrictions
- Advanced actions remain sandboxed or restricted
- Cannot manage users or role assignments
- Cannot perform system-wide administration
Where to use this role?
The Admin role is intended for authorized Arvato internal users only.
Typical users
Authorized Arvato internal users, such as Product Owners.
Includes all permissions from lower levels, plus:
- Configure modules
- Add and maintain module events
- Edit demo payloads
- Copy content between stages
- Manage users
- Assign and change user roles
- Access all administrative Content Builder features
Choosing the Appropriate Role
Always assign the lowest role level that provides the permissions required for the user's responsibilities.
Viewer
Assign the Viewer role when the user only needs to:
- Review available releases
- Preview release content
- Send test emails
Contributor
Assign the Contributor role when the user needs to:
- Maintain content in the frontend
- Import or export content using Excel
- Approve and publish releases
Expert
Assign the Expert role when the user needs to:
- Create or modify templates
- Create advanced content structures
- Use extended Content Builder functionality
Admin
Assign the Expert role when the user needs to:
- Configure modules and events
- Edit demo payloads
- Copy content between stages
- Manage users and role assignments
Recommended approach
Follow the principle of least privilege:
- Assign only the permissions required for the user's responsibilities.
- Limit Admin access to authorized internal users.
- Review role assignments regularly.
- Remove or reduce access when responsibilities change.