This article describes the best way to control access to apps for end users.
Overview
For end users of PhixFlow, it is best to control their access to their apps by:
- 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 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 Action buttons on dashboards.
Considerations for app building
This means that while building the an app, for each type of user you must:
...
Restricting access to dashboards, streams and views can be useful in some cases, but when putting apps together with the method described in this article it is not required, since end users are not able to navigate to these except via action buttons, and their access to actions buttons is controlled. If you restrict access to these components you will need to add these privileges to the relevant user groups, and this can easily become complex and hard to manage.
Controlling access via action buttons
With this in place, access to apps can be controlled as follows:
...