Role-Based Access Control

Role-Based Access Control

GoVista uses RBAC (Role-Based Access Control) to ensure users only access what they need. Here is the complete permission matrix.

Permission Matrix

| Feature | Admin | Editor | Viewer | IT | Regional Mgr | Store Mgr | |---------|-------|--------|--------|-----|-------------|----------| | View Dashboard | Yes | Yes | Yes | Yes | Scoped | Scoped | | Manage Users | Yes | No | No | No | No | No | | Upload Content | Yes | Yes | No | No | Scoped | Scoped | | Create Playlists | Yes | Yes | No | No | Scoped | Scoped | | Create Schedules | Yes | Yes | No | No | Scoped | Scoped | | Approve Content | Yes | No | No | No | Scoped | Scoped | | Add Devices | Yes | No | No | Yes | Scoped | Scoped | | Remote Commands | Yes | No | No | Yes | Scoped | Scoped | | View Analytics | Yes | Yes | Yes | Yes | Scoped | Scoped | | Billing | Yes | No | No | No | No | No | | API Keys | Yes | No | No | No | No | No | | Organization Settings | Yes | No | No | No | No | No |

Scoped Access

Regional Managers and Store Managers have "scoped" access, meaning they can only see and manage resources within their assigned region or store. They cannot access other regions or stores.

How Scoping Works

1. Admin assigns a user to a region or store 2. The user only sees devices, content, and analytics for their scope 3. Content they create is scoped to their area 4. They cannot deploy to devices outside their scope

Custom Permissions

Enterprise plans support custom role definitions:

• Create roles with specific permission combinations
• Name roles to match your organization structure
• Apply custom roles to users

Audit Trail

All actions are logged with the user who performed them:

• Content uploads and edits
• Device commands
• Schedule changes
• User management actions