specs/routes/R_APPP
App Permissions
Overview
The App Permissions page allows users to define which other users are allowed to view, edit, publish or own the app.
By default, all users are “owners” of the app.
There must always be at least one app “Owner”.
When a new App Permission is created, there must be at least one user assigned to the permission.
Model/Page Connections
Create
- A user can create a new permission by pressing the “Add Permission” button in the middle of the screen, choosing a user, then choosing a permission
- A user must press the “checkmark” icon on the right side of the screen to finalize the creation of the permission.
View
- A user can view the list of all users with different app permissions via the list in the middle of the screen
Delete
- A user can delete an individual App Permission by pressing the “x” icon on the right side of the screen related to that permission
View
- A user can view a list of all possible app users after pressing the “Add Permission” button in the middle of the screen.
User Permissions
A user with “owner” permissions for the app can view, edit, create and delete permissions.
A user with “view” permissions for the app can view all permissions.
Tests
| ID | Name |
|---|---|
| QA-T267 | User Roles : 08 - Viewers should be unable to modify data in Tulip |
| QA-T325 | Apps Page : 07 - App Permissions |
Requirements
| ID | Requirement |
|---|---|
| 13 | Provide visibility to approvals or tasks by user, group, role. |
| 114 | The user model includes ability to define access control to all elements of the system including libraries, administration, transactions, functions, apps, integrations, analytics, reporting, etc.c |