Project areas for Global Configuration Management
The configuration lead is responsible for managing configuration hierarchies and must be a member of the Global Configuration Management project area with the Configuration Lead role. This role has permissions to create, modify, and manage the global components and configurations.
The configuration lead must also have at least read access in IBM® Engineering Lifecycle Management application project areas that contribute local configurations. If the same configuration lead needs to create baselines of these local configurations, then they must be a member of the application project areas with a role that grants the create baseline privilege (for example, the Configuration Lead role).
Users who just need to work in the context of a global configuration (and don't need to manage configuration hierarchies) require at least read access to the Global Configuration Management project areas.
Lifecycle projects simplify user management by grouping multiple project areas so that you can manage them and their members from one central location. Select the link in the following table for more information about lifecycle projects.
The links in the table take you to several common topics about configuring project areas.
| To | See |
|---|---|
| Learn about user setup and licensing | Understanding licenses, permissions, and access control |
| Learn about project areas and lifecycle projects | Getting started with project areas and lifecycle projects |
| Create a project area | Create a project area |
| Add users to a project and assign roles | Adding and modifying users |
| Create and modify roles and permissions | Adding and modifying roles and permissions |
| Archive a project area | Archiving and restoring project areas and team areas |