Security Profiles

For example, the user bsmith may be in two different groups in one project and each group may be assigned different security profiles. Bsmith’s security access is then a combination of the two profiles, and she is granted the least restrictive level of permission found in either profile.

Restrictive levels of access

A group can also be assigned more than one security profile in a project. This combined profile contains the least restrictive levels of access available between the two groups. If neither profile covers the requirement type or attribute, the default profile is used.

For example, the Development group is assigned both the Developer and the Tech Support profile

Table 1. Developer Profile
Requirement type Access Level Delete Level Owner Priority Attribute Modification Level
Business Requirements view none none
User Requirements create owned owned
Functional Requirements create any any
Design Requirements create owned owned
Table 2. Tech Support Profile
Requirement type Access Level Delete Level Owner Priority Attribute Modification Level
Business Requirements view none none
User Requirements create owned any
Functional Requirements none none none
Design Requirements none none none
Table 3. Combined Profile
Requirement type Access Level Delete Level Owner Priority Attribute Modification Level
Business Requirements view none none
User Requirements create owned any
Functional Requirements create any any
Design Requirements create owned owned

Permission Set

Members of the Developer group can:
  • view Business requirements
  • create User requirements, delete those they own and modify the Owner Priority attribute in that requirement type

  • create User requirements, delete those they own and modify the Owner Priority attribute in that requirement type

  • create Design requirements, delete requirements that they own, and modify the Owner Priority attribute only if they own the requirement in that type