Creating Security Profiles

There are four steps to creating a security profile:

  • Choose what Requirement Types are assigned to the profile.
  • Choose the Access level for each type, which determines whether group members can see or create requirements of this type.
  • Choose the Delete level for each type, which determines what requirements of a specific type group members can delete.
  • Choose which attributes to assign to each requirement type and set the Modification level for each attribute. The modification level determines when group members can modify the attributes.
Note: Security profiles are shared between projects.

To create a security profile

  1. In the Caliber Administrator, choose File > Admin > Security Profiles from the menu.
  2. In the Security Profiles dialog box, click the New button.
  3. Enter a name and description for the profile. To assign the requirement types to this profile, check the boxes next to the requirement types.
  4. Choose the Access level for the requirements of this type requirement type: None (users cannot see the requirements in this type at all), View (users can only view the requirements of this type, but not create or modify them), or Create (any user can create requirements of this type).
  5. Choose the Delete level for requirements of the requirement type: None (users cannot delete the requirements in this type at all), Owned (users can only delete those requirements of this type that they own), or Any (users can delete any requirements of this type).
  6. Click the Add Attribute(s) button to select which attributes to assign to the selected requirement type. The Attributes dialog box appears.
  7. In the Add Attributes dialog box, select one or more attributes from the list. This adds the attribute to the requirement type within this profile only. If you do not select an attribute for the requirement type, the default profile is used. Click OK to add the attributes.
  8. For each attribute listed in the Modify area, select the circumstances for Modification to determine whether or not users can modify the attribute in requirements of that type: None (users cannot modify the requirements in this type at all), Owned (users can only modify the requirements of this type that they own), or Any (any user can modify any requirement of this type).
  9. Click OK to create the Security Profile.