This article describes the best way to control access to apps for end users.

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.

• Set up an App User role with only essential privileges; see App User.
• Assign application users to the App User role. They will have no access to the repository lists of dashboards, views, streams or any other modelling objects.
• Configure a default dashboard to act as a landing page when user logs into PhixFlow that is, setting a default dashboard for their User.
• Ensure that all the navigation that they require is available in the application's menu options or Action buttons on dashboards.

Create the App User Role 

Anchor
appuser appuser

PhixFlow has a set of pre-configured user roles. However, there is no pre-configured role for an application user.

Application users only need a limited set of privileges to ensure that they can log into the PhixFlow applications that they need to use. Therefore we recommend that you create a specific App User role on your instance of PhixFlow.

1. In the Full Repository, right-click Role and select 

   Insert excerpt
   _add _add nopanel true

   .
2. In the role properties, set Basic Settings → Name to App User.
3. In the Roles section toolbar, click 

   Insert excerpt
   _roles _roles nopanel true

    to open the list of roles.
4. Drag in the following privileges:
   • Run Stream Actions
   • View Applications
   • View Dashboards
   • View Data
   • View Layout Components
   • View Styles
   • View Filters
   • View Menu Items
   • View Menus
   • View Streams
   • View Stream Actions
   • View Stream Views
   • View Styles
5.  Click 

   Insert excerpt
   _finish _finish nopanel true

    to save and close the new role.

Considerations for app building

...