In Contents, users see only the modules and dashboards they’ve been given access to. These modules and dashboards are organized into Functional Areas (meaningful groups that are easy to navigate).
Assigning a user to a role, and limiting that role's access to particular modules and dashboards, ensures that your users see only the data you want them to see. To make this process robust:
- When creating roles, employ a need-to-know approach to data access. This ensures that the roles realistically represent the activities of user groups.
- Build dashboards that are targeted directly to the requirements of the role. It's better to have three simple dashboards, directed to three different roles, rather than one dashboard that displays data that is inappropriate for some users.
Contents fully supports this model of data access — don’t be tempted to avoid Contents and add navigation buttons to dashboards!
Using navigation buttons has implications for data access. For example, when you’re creating navigation buttons on dashboards, even though you may not have access to all dashboards, you can select any dashboard as a target for an Open Dashboard action. Additionally, you might see a small yellow warning triangle when a dashboard tries to display data from a module you don’t have access to. These are indications of poor data protection — using Contents protects against this.