Requirements Management role-based permissions

Edit online

The Requirements Management (RM) application includes the following role-based permissions for project areas.

For a list of permissions that are common to all IBM® Engineering Lifecycle Management (ELM) applications, see Permissions. For instructions on how to access the settings, see Modifying permissions.

Table 1. Project process roles for the Requirements Management application
Project process role Operations and actions Description
Administrator
  • Manage project areas
  • Manage reports
  • Manage server administration
  • Manage users
  • Manage team ownership
  • Manage ReqIF imports
  • Manage artifact and project templates
  • Manage view schedule
  • Modify locks
  • Print reports
  • Manage suspicion profiles
  • Create and delete artifacts
  • Manage artifact types, attributes, data types, and link types
  • Manage reviews, comments, and approval process
  • Create shared filters and views
  • Set link validity
 An Administrator must have a IBM Engineering Requirements Management DOORS® Next (DOORS Next) Analyst client access license (or any client access license with read/write permission).
Author
  • Create and delete artifacts
  • Manage suspicion profiles
  • Print reports
  • Add links to artifacts
  • Create personal and shared tags and apply them to artifacts
  • Comment on artifacts
  • Create personal filters and views
  • Create reviews and approval process
  • Move resources between folders
  • Set link validity
 An Author must have an DOORS Next Analyst client access license.
Commenter
  • Comment on artifacts
  • Create personal tags and apply them to artifacts
  • Create personal filters and views
  • Create or delete review results
 A Commenter must have an DOORS Next Contributor or Analyst client access license (or any client access license with read permission).
Configuration Lead
  • Manage RM project baselines, streams, components, and change sets
 A Configuration Lead must have an DOORS Next Analyst client access license.

Permissions for Requirements Management team areas

Team areas do not inherit all project-area permissions and support only some role-based permissions. However, you can customize permission settings. For details, see Customizing permissions in a team area.
Note: Permissions related to ELM link handling are only supported at the project level. Team areas cannot inherit ELM link handling permissions.
The following project-area permissions are not available for team areas:
  • Clear Suspicion State
  • Create Artifact Template
  • Create Project Template
  • Export ReqIF
  • Import ReqIF
  • Manage ReqIF
  • Manage View Schedule
  • Save any Review
  • Save Artifact Template
  • Save Comment
  • Save Personal Saved View
  • Save Personal Tag
  • Save Review
  • Save Review Approval
  • Save Shared Tag
  • Save Types
  • Set Link Validity