---
title: "Custom Roles"
description: "When and how to define a role that is specific to your organization."
canonical: "https://docs.cm.com/governance/guides/core-concepts/custom-roles"
---

# Custom Roles

> When and how to define a role that is specific to your organization.

Source: https://docs.cm.com/governance/guides/core-concepts/custom-roles

A **custom role** is a role your organization creates itself, by choosing which [permissions](https://docs.cm.com/governance/guides/core-concepts/permissions) it includes.

## When to use one

Use a custom role when the roles that come with Governance give too much, or too little, for a group of people. For example, a role that can view and edit agents but cannot manage users.

## Rules

- A custom role belongs to your organization and can't be used by others.
- The name must be unique within your organization.
- It can only include permissions that exist.
- Creating or changing one needs the Governance Editor permission.
- Changes to a custom role's permissions are recorded in the change log.

## After you create it

A custom role does nothing until you assign it. Assign it to a user or a [team](https://docs.cm.com/governance/guides/core-concepts/teams) like any other role. See [Role assignments](https://docs.cm.com/governance/guides/core-concepts/role-assignments).

## Related

- [Roles](https://docs.cm.com/governance/guides/core-concepts/roles)
- [Permissions](https://docs.cm.com/governance/guides/core-concepts/permissions)