RequirementONE roles and permissions allow you to specify the level of access users should have to your project, and the individual apps within that project.
Permissions available within RequirementONE include:
|Read||Record view access|
|ReadWrite||Record view and edit access|
|ReadWriteAdmin||App and record view, edit and delete access|
Permissions are inherited from the parent. This means for example, that if you assign ReadWriteAdmin permission to the project, you will automatically have ReadWriteAdmin permission to all the apps. Use this table to assign appropriate permissions to each user.
|Add||Task, Record, Issue, Survey, Questionnaire||X||X|
|Delete||Task, Record, Issue, Survey, Questionnaire||X||X|
You can invite up to ten users at a time to a project.
Roles are administrator-defined permission groups that can be assigned to a user. For example, you could create three or more roles with different permission levels according to what those groups of people need to do:
- Blue, Green, Red
- End User, Reviewer, Content Manager
- Developer, Scrum Master, Product Owner
As you invite users, you can assign them to one of the roles.
To make roles work effectively, invite users with a limited set of permissions, and use roles to expand these. Higher permissions always win, therefore, if you have assigned someone ReadWriteAdmin permission to a specification, and then the role allows them only Read permission, the ReadWriteAdmin permission will prevail.
If you decide that you want to use roles, and already have invited users to your system, you should reduce their explicit permissions and invite them to a role.
Now you have configured user access, you might like to: