Skip to main content

FAQ

What is Governance?​

Governance decides who can access what. It supports access based on roles and resources, groups users into teams, and records access logs and change logs. Customers can create their own custom roles. See What is Governance?.

Is Governance replacing the current authorization?​

Yes, in stages rather than all at once.

  • Phase 1: Governance replaces the existing authorization with the Governance API.
  • Phase 2: The Governance UI replaces user management.

Will callers notice a difference?​

No. The response callers get keeps the same shape. What changes is which system works out the decision.

Do all organizations and applications move at the same time?​

No. Organizations and applications are onboarded one by one, and each can switch independently.

Do application teams have to use Governance?​

No. They can keep using platform roles, and need to do nothing. Governance is for teams that want finer control through application-specific roles or resources.

How does an application team get started?​

  1. Your team lead is added to the Governance portal to manage the application's roles.
  2. If you want access by resource, build an endpoint that lists your resources.
  3. Use the libraries Governance provides to check access.

Does an application have to provide resources?​

No. Without a resource endpoint, no resources are listed for that application. Customers can still assign roles without a resource.

Why am I redirected from user management to Governance?​

CM.com does not want several screens for managing users. If you don't need Governance features, you can keep assigning platform roles on the Governance screens as before.