Permission Categories
Permissions are organized into functional categories:Treatment Permissions
Journey Permissions
Analytics Permissions
Agent and AI Insights Permissions
Data Management Permissions
Experience Delivery Permissions
QA Permissions
Admin Permissions
Company Permissions
Standard Role Definitions
Viewer Role
Purpose: Read-only access for stakeholders and observers Permissions:- treatment.view
- program.view
- analyze.objective_view
- analyze.program_view
- datafield.view
- surface.view
- treatment_type.view
- objective.view
Editor Role
Purpose: Day-to-day marketing operations Permissions:- All Viewer permissions, plus:
- treatment.edit
- program.edit
- qa.user_view
- qa.user_edit
Analyst Role
Purpose: Data analysis and reporting Permissions:- All Viewer permissions, plus:
- Agent External Use
- analyze.export
Admin Role
Purpose: Full system administration Permissions:- All permissions
Permission Matrix
Common Permission Scenarios
”I need to create treatments but not manage users”
Recommended Role: Editor Key Permissions: treatment.edit, program.edit”I need to analyze data and use Agent and AI Insights”
Recommended Role: Analyst Key Permissions: analyze.objective_view, analyze.program_view, Agent External Use, analyze.export”I only need to view dashboards for reporting”
Recommended Role: Viewer Key Permissions: treatment.view, program.view, analyze.objective_view, analyze.program_view”I need to set up new surfaces and treatment types”
Recommended Role: Admin (or custom role with specific permissions) Key Permissions: surface.edit, treatment_type.editRequesting Permission Changes
If you need different permissions:- Identify the specific permission(s) you need (use this reference)
- Contact your Console admin
- Explain the business need
- Admin will evaluate and grant if appropriate
Return to Admin Section