Role-based permissions for Global Configuration Management (GCM)

Global Configuration Management (GCM) project areas and team areas have specific role-based permissions that determine which actions you can perform in the application.

For a list of permissions for dashboards, processes, and reports, which are common to all IBM® Engineering Lifecycle Management (ELM) applications, see Permissions. For instructions about how to access the settings, see Modifying role-based permissions.

Table 1. Role-based permissions for Global Configuration Management project areas
Project Process Role Description
Everyone, Contributor Global configurations:
  • In contributing applications, such as the Requirements Management (RM) or Quality Management (QM) application, set the configuration context to a global configuration.
  • Read and use global configurations in the project areas they belong to.

Personal streams: Create, add and remove configurations, modify descriptive properties, scrub, archive, and restore.

Tag Manager Create, rename, and delete tags for configurations and components.

These permissions apply only at the project area level and cannot be assigned to team areas.

A project area administrator might assign this role to team members who are not configuration leads or administrators, so that tags can be managed by multiple team members.

Baseline Maker Contributor permissions plus these permissions:

Baseline staging streams: Create, modify descriptive properties and member configurations (add and remove), commit.

Baselines: Create, modify descriptive properties.

Configuration Lead Tag Manager, Baseline Maker, and Contributor permissions plus these permissions:

Baseline staging streams: Archive and restore.

Baselines: Archive and restore.

Components: Archive and restore, create, and modify component properties.

Shared queries: Create.

Streams: Create from both streams and baselines, archive and restore, modify descriptive properties and member configurations (add and remove).
Important: Creating a stream from another stream does not create a baseline. If your organization must capture a frozen set of artifacts for auditing or regulatory purposes, you might assign this privilege to only a few team members. Teams might use this capability to create temporary streams for experiments, and these streams are not intended to replace the original stream.

Type definitions (artifact types, attributes, data types, and link types): Create and modify.

Administrator Tag Manager and Configuration Lead permissions plus these permissions:

Classified or sensitive information: Scrub or remove from components, global configurations, baseline staging streams, and personal streams.

Shared queries: Modify and delete queries created by others.

Team members' personal streams: Archive and restore, modify descriptive properties and member configurations (add and remove), scrub, view.

Type definitions (artifact types, attributes, data types, and link types): Import and modify imported final type definitions.


video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki