...
When creating an app two user groups are created to help control access, see flow 2.5 the notes cover the logic. This will influence the wording on this page.
We also need to review controlling access to action buttons as we are now moving to ActionFlows. Comments in green below
...
- In the Full Repository, right-click Role and select
.Insert excerpt _new _new nopanel true - In the role properties, set Basic Settings → Name to
App User
. - In the Roles section toolbar, click
to open the list of roles.Insert excerpt _roles _roles nopanel true - 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
- Click
to save and close the new role.Insert excerpt _finish _finish nopanel true - Add the App User role to the user groups that need access to the application. We need to confirm if this is now automatically added to the App Name user group that gets auto-created.
Planning User Access to Screens
...