Skip to content

Roles & Permissions

Roles define what users can do. Each role has specific permissions controlling access to features and actions.

Highest permission level with full system access.

Capabilities:

  • All Staff capabilities
  • Manage users and roles
  • Configure integrations
  • Access billing and subscription
  • Manage company settings
  • Create and manage share links
  • Access audit logs

Best for: Business owners, IT managers, system administrators

Elevated access for power users who manage data and dashboards.

Capabilities:

  • All Member capabilities
  • Create and delete dashboards
  • Create and manage widgets
  • Configure data sources
  • Create Modified and Joined Datasets
  • Manage dashboard templates
  • Create share links

Best for: Analysts, department leads, power users

Standard access for regular team members.

Capabilities:

  • View assigned dashboards
  • Interact with filters and dashboard controls
  • Export data from widgets
  • Manage personal settings
  • Read-only access to most features unless explicitly overridden

Best for: General employees, team members

Section titled “ShareLinks (external access, not a user role)”

ShareLinks are public or restricted dashboard links for people outside your account. They are not assignable user roles.

Use this for: Clients, external stakeholders, and read-only sharing without creating a user account

ActionAdminStaffMember
View dashboardsYesYesYes
Create dashboardsYesYes-
Edit dashboardsYesYes-
Delete dashboardsYesYes-
Share dashboardsYesYes-
ActionAdminStaffMember
View widgetsYesYesYes
Create widgetsYesYes-
Edit widgetsYesYes-
Delete widgetsYesYes-
ActionAdminStaffMember
View datasetsYesYes-
Create Modified DatasetsYesYes-
Create Joined DatasetsYesYes-
Manage integrationsYesYes-
Access Data LineageYesYes-
ActionAdminStaffMember
Manage usersYesYes-
Assign rolesYesYes-
Manage dashboard groupsYesYes-
Access billingYes--
Company settingsYes--
Audit logsYes--
  1. Create the new user
  2. Select their role from the dropdown
  3. Role applies immediately
  1. Go to User Management
  2. Edit the user
  3. Change the role
  4. Save changes
  5. New permissions apply immediately

Promoting a user:

  • They gain immediate access to new capabilities
  • Review their dashboard group assignments

Demoting a user:

  • They lose privileged features immediately
  • Items they created remain
  • Consider handoff for administrative responsibilities
  • Start restrictive: Begin with lower roles, upgrade as needed
  • Least privilege: Give only necessary access
  • Regular review: Audit roles periodically
  • Limit the number of Admins
  • Ensure at least two Admins for coverage
  • Use strong passwords and 2FA
  • Assign to users who actively manage data
  • Don’t use for view-only users
  • Consider the workload impact
  • Member is the default role for most internal users
  • Use ShareLinks for external stakeholders who should not get a user account
  • Keep members focused on viewing and interacting, not managing configuration

The initial account creator is always Admin and can’t be demoted or removed without transferring ownership.

You can’t remove or demote the last Admin. Ensure another Admin exists first.

Admins can demote themselves, but only if another Admin exists.

Admins can restrict which datasets each user can access and what they can do with them. This is available on Professional, Business, and Starship tiers.

  • Full access - User sees all datasets (default)
  • Blacklist - User sees all datasets EXCEPT those explicitly excluded
  • Whitelist - User sees ONLY datasets explicitly included
  • Read & Write - User can view and use the dataset (widgets, modified datasets, joined datasets) and also edit the dataset
  • Read Only - User can view and use the dataset (widgets, modified datasets, joined datasets) but cannot edit the dataset

In the edit-user page, dataset permissions are controlled with:

  • Access Mode
  • Default Permission Level
  • Allowed / Blocked Datasets
  • Per-Dataset Permission Overrides in whitelist mode for non-members

Dataset permissions filter what appears in:

  • Data Management → Datasets list
  • Dataset selector when creating widgets
  • Data Studio and Modified Dataset editor
  • Data Lineage view

Role-specific behavior:

  • Admin users always bypass these restrictions and keep full read/write access.
  • Staff users can use the full dataset permission UI.
  • Member users use dataset permissions only inside AI Chat. They still cannot open the raw Datasets or Modified Datasets pages directly, and their dataset access remains Read Only.

Admins can control feature access and write actions per user from the toggle list on the edit-user page. By default, staff can write to most features and members stay limited, but these defaults can be overridden. Use Reset to Role Defaults in the UI to restore the standard role behavior.

  • Dashboards & Widgets
  • Integrations
  • Modified Datasets
  • Dynamic Filter Variables
  • Share Links
  • Resplendent API
  • Custom Integrations
  • Templates
  • Reports
  • Widget Snapshots
  • Soundboard
  • Tags
  • AI Chat Access
  • AI Context Updates
ToggleWhat it controls
Dashboards & WidgetsDashboard and widget editing actions
IntegrationsAdding, editing, and reconnecting standard integrations
Modified DatasetsCreating and editing Modified Datasets
Dynamic Filter VariablesCreating, editing, and deleting filter variables
Share LinksCreating and managing share links
Resplendent APIManaging API credentials
Custom IntegrationsCreating and editing custom integrations
TemplatesManaging dashboard and widget templates
ReportsReport blueprint and report-related editing actions
Widget SnapshotsWidget snapshot creation and deletion actions
SoundboardThreshold alert sound management
TagsTag management
AI Chat AccessAccess to Eric / AI Chat
AI Context UpdatesSubmitting AI context updates from supported dataset prompts

Important behavior:

  • Turning a toggle off usually makes that feature read-only or disables its management actions.
  • Some pages may still be visible while their edit controls are disabled.
  • Tier limits and role requirements can still restrict separate actions even if the toggle is on.
  • AI Chat Access defaults on for Admins and Giga Admins in beta companies, but not for Staff or Members.
  • AI Context Updates defaults on for Staff and above in beta companies.
  • Members only get the AI Chat Access toggle.
  • AI Chat Access and AI Context Updates only appear for beta companies (or Giga Admins).

Read-only users still see disabled buttons and actions. They can continue to view data, export from widgets, and use filters where their role allows it.

Roles work with Dashboard Groups and permissions:

  • Role defines what you can do by default
  • Dashboard Groups define what dashboards you can see
  • Dataset permissions define what data you can access
  • Feature permissions define which features you can modify
  • All layers must allow an action for it to be permitted

Example:

  • A Member in the “Sales” group can view Sales dashboards
  • A Member with dataset whitelist can only see whitelisted datasets in widgets
  • A Member with read-only dashboard permission can view but not edit any dashboard
  1. Check their role in User Management
  2. Verify the role has that permission
  3. Check dashboard group assignments
  4. Check feature permissions (Professional+)
  5. Review any specific restrictions
  1. Check if dataset permissions are configured (Professional+)
  2. Verify the user is not in whitelist mode without that dataset included
  3. Check if the dataset is blacklisted for this user
  4. Confirm the user has at least read access to the parent table
  • Ensure changes were saved
  • User may need to refresh their browser
  • Log out and back in to reset session
  • Review role assignment
  • Check dashboard group memberships
  • Audit recent role changes
  • Review dataset and feature permission overrides

If buttons or actions appear disabled:

  1. Check the user’s role and assigned permissions
  2. Verify feature permissions are not set to read-only
  3. For dataset operations, check dataset-level permissions
  4. Remember that members are read-only by default for most features