Allow users with different access rights to open dashboards with data from different data sources without having to react to warnings or error messages.
This is an option that the Designer user can enable on the document or on individual objects that would otherwise show up as an error if a user does not have the necessary access rights to see all data in the object.
Enabling this option can be done for the entire document (all objects) or it can be set per individual object. The object specific settings will override the document setting - i.e. if the document is set to hide inaccessible documents, you can choose that one specific object should still fail (show a warning/error message).
The options to hide inaccessible objects are available from the Criteria Smartpad (by default, everything is disabled):
When enabled, users with proper access rights will see the object as usual, while users with missing access rights will not see the object - nor will they see the usual warnings or error messages. In fact, for the latter type of users, the object will not exist when opening the document.
Note: If the document setting 'Hide all inaccessible objects' is enabled, criteria coming from dimensions that are inaccessible will also be removed.
Warning: If you, as a Designer user, opens a document that contains elements that you do not have access to, and you then try to save the document, you will actually be saving it without the hidden objects. If you should try to save a document in this way, you will also get a warning before actually saving it:
As noted in the warning, you, as a Designer user, can open the document without data to avoid the automatic removals:
Tip: If designed cleverly, another, layered object could become visible when the initial object is hidden. It could be a different KPI object - or it could be an alternative warning message (created as a Text box), as in this example:
'Hide if inaccessible' will also work for objects in a report. However, if a report contains an iteration, and the data used for that iteration is inaccessible, the report will still fail. 'Hide if inaccessible' has no effect on iterations.