Reading time 2 mins
Introduction
- When sharing a dashboard with a user it is granting them access to view the information held within the data source (commonly referred to as the ‘cube’).
- For example, if you have built a dashboard using your Event data ‘cube’ then by sharing this dashboard into Radar Healthcare and granting permission for a user to see that dashboard they are granted access to view the Event date ‘cube.’ This allows them to see the data displayed in your dashboard.
- If you then share a dashboard with the same cube as its source at a lower scope, then the system (because user already has access to the entire cube) will allow that user to see data from the highest scope.
- To address this, we introduced the concept of ‘OID’ filters. This is filtering the permissions based on the dashboard itself rather than the cube.
Applying Dashboard OID
- In below example we have 2 dashboards using data from the same data ‘cube’ and these have been shared to 1 user at 2 different scopes, therefore, this user will see Organisational wide data in both dashboards.
- Every dashboard has a UNIQUE ID which is contained in the URL in the builder.
- To ensure permission apply at a dashboard level we need to add this as a filter to the dashboard.
- When we add the filter, we now need to restrict it to this dashboard (copy and paste the GUID from URL.
- Please note, once applied this filter will not affect any data/presentation on the dashboard.
- Once done set as a background filter then lock so users cannot amend.
- This change now means the scope is applied at the dashboard level not the data ‘cube’ level and as such users will only see data based on the scope at which the dashboard was shared via Access Control.
