Setup, permissions and authorization

Permissions

Standard user access rules in dRofus do not apply to users of ReqHub. Within a task in the Collector app, users can modify all data defined by the associated requirement set.

For example, even if a user only has read access to Items in dRofus, the same user can still enter values into the fields of occurrences included in the requirement set. In the Collector app, edit access is determined by visibility:
If you can see the field (because it is part of the requirement set), you can edit its values.

Authorization

Authorization behaves differently between the Manager and Collector apps. However, both share a common requirement: the user must be a registered dRofus user.

Manager

To access Manager, the user must have Admin access to the project. Admins can view all requirement sets created in the project and have full privileges to create, read, update, and delete (CRUD) these requirement sets.

Collector

When a manager creates a requirement set in Manager, it is linked to a responsibility group. Any project user with access to that responsibility group gains access to the related requirement sets and their associated tasks in Collector.

In practice:

• Users of Collector are authorized through their assigned responsibility groups.

• Each requirement set is connected to one responsibility group.

• Users are mapped to responsibility groups via the admin system.

As a result, a responsibility defines a group of users collaborating within the same requirement ruleset.