Troubleshooting user permissions
Omni offers a powerful set of user roles and the permissions to control your users' experience, but sometimes understanding all the nuances of permissions can cause confusion.
In this guide, we'll show you how to troubleshoot the most common permissions questions we see arise with our customers.
If there's a troubleshooting question or scenario you want to see here, reach out to Omni support.
Can't display chart dashboard error
What it looks like | Restricted Queriers and Viewers see Can't display chart errors when viewing a dashboard |
Why it happens | This is typically due to Omni enforcing connection roles when content in a dashboard is built outside of a topic. |
How to fix it | In this video, we explain what's happening and how to resolve it using Omni's AccessBoost feature. |
No option to view workbook
What it looks like | Viewers don't have the option to view a workbook in a document |
Why it happens | By default, the workbooks are not accessible to Viewers. Omni does this because Viewers don't have the ability to build in workbooks. |
How to fix it | Enable document ability (organization-level)Organization Admins can change this default behavior in Settings > General > Content permissions with the Viewers can see workbook setting. Click the toggle in the Ability column
![]() Enable for individual documentsWorkbook access for Viewers can also be enabled on indidvidual documents in Share > Settings and enabling Viewers can see workbook. Note: This requires the organization-level version of this setting to be enabled. ![]() |
You don't have access to this tab workbook error
What it looks like | Users see You don't have access to this tab messages when viewing a workbook tab ![]() |
Why it happens | Similar to not being able to see data on a dashboard, this happens when one of the workbook tabs:
|
How to fix it | To resolve the error, the query associated with the tab must be rebuilt using a topic. Omni's AccessBoost feature can be enabled, which would ignore data permissions usually enforced by connection roles, but this would only show the data on the dashboard not the query in the workbook. |
Unable to view specific topics
What it looks like | User is unable to view a specific topic |
Why it happens | Topic visibility is primarily controlled by access grants, which are a permissions systems configured in the model file and then called as a required_access_grant within a topic to enforce which users are able to see a given topic. |
How to fix it | Access grants can be built to evaluate user attributes or user groups to determine which users will return a true value for the access grant. Access grants and user groups are definied within Omni Settings and often set for a given user as part of a log-in process into Omni. |
Restricted Queriers are unable to add topic joins
What it looks like | While in a workbook, a Restricted Querier is denied access to adding joins to a topic |
Why it happens | Restricted Queriers are only able to build in a workbook using topics, which scopes their access to the data available in the database to the joins, filters and permissions configured in topics. Adding another table into a topic would effectively be bringing net new data into a topic, which is outside of the permissions scope for a Restricted Querier. |
How to fix it If you want a user to be able to add joins to a topic, elevate their permissions to Querier or higher. |
Ownership changes after moving document
What it looks like | A user is no longer the owner of a document after moving the document to a shared folder. |
Why it happens | At a high level, the parent folder dictates the inherited permissions of the folders and dashboards contained in the parent folder. This means that each child folder or dashboard can have the same or higher permissions as the parent folder. Additionally, when documents are moved to a shared folder or subfolder, their ownership will change to the user who owns the folder. Refer to the Access inheritance guide for more information. |
How to fix it | To retain ownership of a document, users should:
|
Locked filters for Viewers or Embed users
What it looks like | Viewers or Embed users are unable to change filters on a dashboard |
Why it happens | Often when a dashboard has a filter applied, a locked filter is the result of an access filters being enforced. Access filters are used to enforce row-level security - for example, in an embedded Omni instance that is built on a multi-tenant database. Access filters are created in a topic file by defining a field to be filtered and then reading the value of a specificed user attribute. All values except the one specified in the access grant will be filtered out - think of this as a SQL |
How to fix it |
|