# Get Role

See exactly what one role lets its members do, permission by permission.

`GET https://connect.mindcloud.co/v2/roles/:roleId`

Permissions: `member:view`.

## Parameters

### Path

- `roleId` (string, required): The role's id, from List Roles.

### Headers

- `X-Company-Id` (string): Optional. The id of the organization to act in. Leave it out to act in the API key's own organization. A key can also act in its child organizations, and, with "Use this key across all of your organizations" on, in every organization its creator can open in the app. List them with GET /v2/companies. Every response's X-Company-Id header names the organization it acted in. See [Organizations](https://mindcloud.co/docs/api/rest/introduction/organizations).

## Example request

```bash
curl --request GET \
  --url 'https://connect.mindcloud.co/v2/roles/Rl5wB9cF3hJp' \
  --header 'Authorization: Bearer $MINDCLOUD_API_TOKEN'
```

## Response fields

- `id` (string): Unique id of the role.
- `name` (string): The role's name.
- `description` (string): The role's description. Empty when nobody wrote one.
- `isAdmin` (boolean): True if the role grants admin rights.
- `isGlobal` (boolean): True for roles MindCloud provides to every company. Global roles are read-only: writing one answers 404.
- `createdOn` (date): When the role was created.
- `memberCount` (number): How many people in the company hold the role, people whose invite is pending included. A role with members cannot be deleted.
- `permissions` (array of objects): Everything the role allows, as { key, name } pairs.
  - `key` (string): The permission key, such as workflow:run.
  - `name` (string): The permission's display name.