With BriefBuilder’s roles settings, you can control users’ permissions in relation to verifications. In this article, we will explain how it works, covering the following topics:
- Verification permissions in general
- Default verification roles
- Creating your own roles
Permissions
To manage verification permissions, you have to access the roles settings in your model:
Navigation bar > Settings > Project model > Roles
In the roles menu, there are three headers (columns) that are relevant for verification:
- (Verification) plan
- (Verification) result
- Demonstration documents
Each of these topics comes with a set of permissions, signified by the small icons in the table. When a permission is activated, the icon is blue. If not, it is grey. See below for an explanation of each icon.
Verification plan
| Configure | Allows you to configure the settings of the verification plan (i.e. defining verification methods and verification phases) |
| Edit | Allows you to add and edit the content of the verification plan (e.g. defining when, how, and by whom requirements should be verified) |
Verification result
| Configure | Allows you to configure the settings of the verification result (i.e. result categories, like compliant, non-compliant, partially compliant) |
| Edit all objects | Allows you to add and edit all verification results |
| Edit assigned objects | Allows you to add and edit only those verification results that are specifically assigned to you |
Demonstration documents
| Configure | Allows you to configure the standard properties of the demonstration document (i.e. format or author) |
| Edit | Allows you to create, edit and delete demonstration document objects in the demonstration document tree |
| Comment | Allows you to make comments regarding demonstration documents |
Default roles
Using the permissions above, we have created a set of default verification roles to help you on your way. You always get these when you create a new project model. Below, we will explain each of these roles.
Requirements manager
This role is not specifically targeted at verification, but it is a good one to be aware of as this role has all permissions for the model, and thus also all permissions in relation to verification. It is a role that will be only relevant for a few people (e.g. the project’s quality manager).
Verification manager
This role is for those that are in charge of setting up and organizing the verification process. They can configure and develop the verification plans, configure the set-up for verification results (e.g. outcome categories), and configure the set-up for the demonstration documents.
Verification editor
This role has the Edit all objects permission for verification results. This means that people who have this role can edit the verification results for all requirements. Very flexible, also somewhat blunt.
Verification executor
This role is similar to the above, but only for assigned verifications (it has the permission Edit assigned objects for verification results). This means that if a user only has this role, they can only edit verification results that they have been explicitly assigned to.
Of the above, the Verification executor role is the most suitable for users who have no other business in BriefBuilder other than viewing requirements and doing verifications. As explained above, it allows them to edit only their own verifications, and not those of others.
Good to know: we have made a dedicated explanation video for this target group: Quick guide to verification.
Creating your own verification roles
Instead of using the default roles, you can also decide to create your own roles. For example, roles that are similar to people’s functional role within the project. E.g. architect, contractor, electrical engineer, and so on.
For all these roles you can then define which permissions they should have in relation to verification.
In most cases, the earlier mentioned Edit assigned objects permission will be the one most suitable, as it limits edit rights to the verifications that have been explicitly assigned to users. See screendump below.
Important: input type for responsible
In order to properly use the Edit assigned permission, you need to make sure that the verification plan’s standard property Responsible is configured with input type ‘User / Role / Organisation‘.
This input type is the default setting, but it is possible to change it (e.g. to picklist). Our recommendation, however, is not to do that because then you will no longer be able to assign verifications to specific users.
You can check this setting in in the Settings menu:
Settings menu > Verification > Standard properties > Verification plan
Once you have done that, you can work on your verification plan and assign verifications to the right people.
Note that there are three way to do this. You can assign a verification to:
- a user (e.g., assigned to Timothy Jackson)
- an organisation (e.g., assigned to organisation BriefBuilder)
- a role (e.g., assigned to role Architect)
If you assign a verification to an organisation, it will be editable for all the persons that are part of that organisation.
Likewise, if you assign a verification to a role, it will be editable for all the persons that have been given that role.