Setting permissions for configurations in RM and QM project areas

Control which team members can do configuration-related tasks by using the Configuration Management group of permissions for that Requirements Management (RM) or Quality Management (QM) project area. The permissions that you assign apply to all the configurations (streams and baselines) in a project area. You cannot assign permissions for specific local configurations.

Before you begin

  • You must have permission to modify the RM or QM project area.

About this task

You can assign permissions by role or by operation, and configure permissions for a specific time period. See Modifying Permissions.

Role names might differ across IBM Engineering Lifecycle Management (ELM) applications. See the related link for details about a specific ELM application.

If configuration management is not enabled for a project area, an administrator controls access to baseline-related tasks by using the baseline-related permissions in the Configuration Management permission group.

If your project uses global configurations, you must grant Configuration Leads (from the Global Configuration Management (GCM) application) permission in RM and QM project areas to create streams and baselines. Without this permission, automatic configuration creation features in GCM do not work, and the configuration lead must contact an RM and QM project lead to manually create the local configurations; then, the Configuration lead must manually add them to the global configuration.

RM and QM team members must be members of the GCM project area that contains the global configurations that they work with. Permissions for global configurations are managed at the project area level in the GCM application. For more information, see the related links.

QM only: By default, all permissions in the Configuration Management group are disabled and you must assign them manually. For example, you might create a new role to assign to team members. Configuration-related tasks include managing streams, baselines, and components, cloning artifacts, merging configurations, and restoring a stream with a baseline.


  1. Navigate to the properties page of a project area. For example:
    1. Click the Administration menu Administration menu near the upper right, and click Manage Project Areas.
    2. Click the project area whose permissions you want to manage.
  2. Click Permissions, and expand the Configuration Management group of permissions.
  3. Grant or revoke the permissions that are required by your project; then, click Save.

What to do next

The permissions are effective immediately. If you plan to add local configurations from ELM applications to global configurations, some setup is required, and permissions are managed separately. See the related topics.