Roles

The various tasks required to install, configure, or use IBM Cloud Pak® for Integration may be performed by different roles within the enterprise. These roles will vary depending on factors such as skill sets and permissions.

Default roles

Note: The default admin user cannot upgrade deployed instances of Cloud Pak for Integration capabilities in the deployment and navigation interface (Platform Navigator). To do so, they must have the automation_administrator permission added (via the User management page).

A Cluster administrator should be able to allocate CPU, memory and storage to nodes, arrange for DNS resolution and install new software.

An Automation administrator should be able to deploy new Integration capabilities within the IBM Cloud Pak for Integration, and then use those capabilities to create Integrations.

The Automation administrator must have:

Administrator permission on one or more namespaces into which they will be deploying products.
(If you have not yet migrated to using operator-based deployments): Permission to use the local-charts helm repository, so you can access the helm charts required for installations.

An Automation operator, Automation developer, and Automation analyst can use installed capabilities, but they are not able to deploy new Integration capabilities within the IBM Cloud Pak for Integration to create Integrations.

Custom roles

An Administrator can create custom roles on the User management page. On the IBM Automation home page (Platform Navigator), click Manage users. Click the Roles tab, then click the New role button. Enter a name for the new role along with an optional description. Next, select the permissions to apply to the new role. Finally, click Create. Once the custom roles are created, they can be applied when adding new users.