User roles

In BriefBuilder, you can assign user roles on two levels:

Environment level: What is a user allowed to do/see within the client environment?
Project level: What is a user allowed to do/see within a particular project model?

Environment roles

On an environment level, there are three roles to choose from:

Project participant

This is default role when you add a new user. This role is typically assigned to people who should only have access to one or more specific projects. It typically concerns external parties (e.g. architect or engineers of a specific project).

Access to one or more particular projects

Please note: this user cannot see or edit any project until he or she has been given a specific role for that project.

Environment editor

This role is typically assigned to people working within the client organisation who work with BriefBuilder on a regular basis. They can see the projects of their colleagues and can clone/create new projects for themselves.

Create new projects
Clone projects
View all projects in the environment (active and archived)

Environment administrator

This role is reserved for the BriefBuilder ‘super user’ within the organisation: the one that knows most about BriefBuilder, does user management, and helps his or her colleagues in the use of BriefBuilder.

Same as Environment editor, plus
Delete projects
Archive projects, restore archived projects
View and restore back-ups
User management

Project roles

On a project level, there are five different roles to choose from:

Owner

This role is automatically assigned to the person who creates the project. It allows you to administer the project and to view and edit all the data in it.

Editing the project homepage
Edit all settings (requirements/analysis/verification/RFC/user roles/modules)
Edit all data (project name/requirements/analysis/verification plan/outcomes/RFC-request/RFC-assessment)
Import objects/trees from other projects (active and archived)
Versioning and publishing
Add modules
Create comments
View audit/history

Editor

This role gives you to possibility to edit specific parts of the project.

Edit part(s) of the project. Options:
Requirements
Analysis
Verification plan
Verification outcomes
RFC request
RFC assessment
Import objects/trees from other projects (active and archived)
View all versions
Create comments
View audit/history

Viewer with comments

This role allows you to see all versions and all changes, and to make comments.

Create and view comments
View all versions
View audit/history

Viewer all versions

This role allows you to see all versions and changes.

View all versions
View audit/history

Viewer published versions

With this role you can only see the published versions. No comment possibilities. No insights in project history.

View published versions only

Please note: in formal tender procedures, the ‘viewer published versions’ is the most appropriate one for parties participating in the tender. They only get to see the ‘officially’ published data.

Was this article helpful?

Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
CONTACT SUPPORT

Leave a Comment