Standard license consumption

A legacy license model Standard license in Collibra grants users broader access and functionality compared to a Read-only licenses. This license level allows holders to actively interact with the platform, performing tasks and activities such as creating and editing assets, participating in workflows, and contributing to data governance processes.

Important This license type is available only if you have a legacy license model.

Note There is currently a known issue with Edge only system users consuming a Standard license. We will allow all customers to exceed the license agreement for such Edge only users until this known issue has been fixed.

Occupying a standard license seat

Each global or resource permission in a Collibra environment with a legacy license model requires either a Standard or a Read-only license. The required license for each permission is visible under Settings → Roles and Permissions → Global Permissions or Settings → Roles and Permissions→ Resource Permissions.

A role corresponds to a set of permissions. If the role contains at least one permission that requires a Standard license, then the role requires a Standard license.

The aggregate license requirement for each role is visible under Settings → Roles and Permissions→ Global Roles or Settings → Roles and Permissions→ Resource Roles.

Roles are assigned to users through a group or directly. If the user has at least one role that requires a Standard license, then the user is occupying a Standard license seat. This is known as the required license of a user.

Global roles are assigned in Settings, and resource roles are assigned at the community, domain, or asset level, referred to as assigned responsibilities.

With the 2021 license model, a user with a Read-only required license participating in a workflow during a given calendar month effectively occupies a Standard license until the end of that month. This is known as the effective license of a user.

Verify why a specific user requires a Standard license

Important 

In Collibra 2024.05, we launched a new user interface (UI) for Collibra Platform! You can learn more about this latest UI in the UI overview.

Use the following options to see the documentation in the latest UI or in the previous, classic UI:

  • Global roles
  • Resource roles
  1. Go to Settings → Users and Subscriptions → Users.
  2. Find the user that requires a Standard license and click their name.
  3. On the user profile page, click the Groups tab to see the list of groups the user belongs to.
  4. Add the Required License column to view the license each group requires.
  1. Go to Settings → Users and groups → Users.
  2. Find the user that requires a Standard license and click their name.
  3. On the user profile page, click the Groups tab to see the list of groups the user belongs to.
  4. In a separate browser, go to Settings → Global roles.
  5. Each listed role indicates whether it requires a Standard or Read-only license.
  6. Verify if the user or one of their groups is assigned to a global role that requires a Standard license.
  1. Go to Settings → Users and Subscriptions → Users.
  2. Find the user that requires a Standard license and click their name.
  3. On the user profile page, click the Responsibilities tab to see a list of the responsibilities the user has.
  4. Each responsibility shows the required license.
  1. Go to Settings → Users and groups → Users.
  2. Find the user that requires a Standard license and click on their name.
  3. On the user profile page, click the Responsibilities tab to see a list of the responsibilities the user has.
  4. In a separate browser, go to Settings → Resource roles.
  5. Each listed role indicates whether it requires a Standard or Read-only license.
  6. Verify the responsibilities that require a Standard license.

Update a Standard license to a Read-only license

Remove the user from any groups or responsibilities that require a Standard license to update a user from a Standard license to a Read-only license.

Note  If you have SSO enabled, depending on the configuration of the system, removing a user from a group may require a change in the connected LDAP system.