This article describes the best way to control access to apps for end users.
When creating an app two user groups are created to help control access, see flow 2.5 the notes cover the logic.
We also need to review controlling access to action buttons as we are now moving to ActionFlows. Comments in green below
Overview
For end users of a PhixFlow application, we recommend that access to PhixFlow itself is restricted. You can ensure that users can only access applications as follows.
...
| Note |
|---|
This can easily become complex and hard to manage. |
Controlling Access Using Action Buttons can we have an example?
- Create a set of user groups to represent all application user roles.
- To each user group add access to the actions buttons that the group of users need to access
- tasks
- other dashboards
- Only associate the privileges specifically for this role, not for this role and everything “underneath” it. What does this mean?
- At least one user group must contain the App User role.
- Layer the user groups onto the users so that they end up with the access they need.
...