Roles And Permissions

Builder Insights uses a shared role model across the mobile app and admin portal.

Role hierarchy

Role	Level	Summary
Administrator	100	Full access, including user management, settings, and admin-only operations
Manager	75	Team-level access, broader editing, event management, imports, and executive visibility
Advocate	50	Standard capture and contribution role
Viewer	25	Read-only access to system data

Shared role expectations

Viewer

• can view insights and events
• can view analytics and dashboards
• cannot create or modify data
• should be treated as read-only in both products

Advocate

• can create insights
• can edit their own insights
• can participate in normal capture workflows
• can view team data

Manager

• can edit all insights
• can manage events
• can access manager-level workflows such as imports
• can access executive-level views

Administrator

• has all manager permissions
• can manage users
• can access admin-only settings and operations

Mobile app implications

• Executive tab is visible only for manager and admin
• standard field capture is intended for advocate-and-above roles
• profile should reflect the active user role clearly

Admin portal implications

• /operations and /admin areas require admin access
• manager-level paths such as import require at least manager
• viewers can read but should not be allowed mutation workflows
• mutation APIs for key entities require at least advocate

Practical testing guidance

When role-specific accounts are not available:

• test with the demo account for general behavior
• note role-gated paths as not verified
• do not assume visibility or access rules are correct without the proper role

Related references

• Shared Platform > Data Model And API
• Operations > QA Tester Guide