...
- Giving users the App User role - that means that they have no access to the lists of dashboards, views, streams or any other modelling components in the left-hand menu bar Repository Browser
- Giving them a "landing page" - that is, setting a default dashboard for their User
- All navigation from that point being only by pressing actions buttons on pressing Action buttons on dashboards.
Considerations for app building
...
- Build up a series of user groups that represent roles
- To each user group add access to the actions buttons that give access to the tasks and routes to other dashboards required by this role – only associate the privileges specifically for this role, not for this role and everything “underneath” it
- At least one user group must contain the role App User - for clarity, it is best if the App User is only in one of the user groups added for users (commonly via an "App User" user group)
- Layer the user groups onto the users so that they end up with the access they need
...