Skip to main content

Catalog RBAC

For IDP 1.0 Customers

This RBAC guide is applicable only to IDP 2.0 customers, as the RBAC Harness platform hierarchy is available exclusively in IDP 2.0.

With the release of Granular RBAC in IDP 2.0, you can now control access to your Catalog entities—i.e., you can restrict who can create and view these entities. Catalog entities can be created at all available scopes: Account, Org, or Project. To learn more about entities, permissions, and scopes, visit the IDP 2.0 Data Model.

For IDP 2.0 Customers

If you're using Harness IDP 2.0, please ensure you have reviewed the IDP 2.0 Overview guide and are familiar with the key steps for upgrading to IDP 2.0. To enable IDP 2.0, you must raise a support ticket to activate the IDP_2_0 feature flag for your account.

RBAC Workflow in Harness IDP

Before configuring RBAC for your Catalog entities, ensure you’ve reviewed the documentation on Scopes, Permissions, and different RBAC Components.

Here’s the workflow for configuring RBAC in Harness IDP:

  1. Go to your administrative settings and select the scope (Account, Org, or Project) at which you want to configure RBAC.
  2. Create roles with the desired permissions. Example: If you are configuring RBAC for Catalog entity creation, ensure the role has the Create/Edit (Catalog) permission enabled.
  3. Create resource groups to apply RBAC to a specific set of resources for the principal. Example: To configure RBAC for Catalog entities, ensure the Catalog resource is added to the resource group.
  4. Create user groups and add users.
  5. Assign roles and resource groups to users or user groups.
  6. If you haven’t already, configure authentication.

Permissions for Catalog Entities

All core Catalog entities (Component, API, Resource) fall under the "Catalog" resource category for RBAC. The following permissions can be configured when creating a custom role:

PermissionDescription
Create/EditAllows users to create Catalog entities and modify their configuration.
ViewAllows users to view Catalog entities but not create, modify, or delete them.
DeleteAllows users to delete Catalog entities.

These permissions can be configured when creating a custom role. Select the desired permissions based on the level of access you want to grant. To learn more, see Manage Roles.

Image

Catalog RBAC Example

Configure RBAC for Account-Level Catalog Entity Creation

This example shows how to configure RBAC to allow full control over Catalog entity creation and modification at the Account scope (including all child resources).

In this example, we use:

  • A custom role: IDP Catalog Create
  • (Optional) A custom resource group: All Catalog Create Resources
  • (Optional) A custom user group: Catalog Create Users

The All Catalog Create Resources group exists at the Account scope and provides Create/Edit access to all Catalog entities across the account, including all organizations and projects. The IDP Catalog Create role includes the Create/Edit permission for Catalog resources.

You can access Administrative Settings from your Harness UI directly using the sidenavbar.


Step 1: Create the IDP Catalog Creator Role

Learn more about roles: Manage roles | Permissions reference


(Optional) Step 2: Create a custom Resource Group

Learn more: Manage resource groups


(Optional) Step 3: Create the "Catalog Create Users" User Group

Learn more: Manage user groups | Manage users


Step 4: Assign the Role and Resource Group to the User Group

Learn more: Role binding

This setup configures RBAC so that users in the Catalog Create Users group have Create/Edit access to Catalog entities at the Account scope, as well as within all Organizations and Projects under the account.