List Permissions
See every permission you can build a role or an API key from, and which of them a custom role may carry. Use the keys in Create Role, Update Role, and Create API Key.
Headers
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.
Query
RSQL expression used to filter list results.
Maximum number of rows to return.
Number of rows to skip.
Comma-separated sort fields; prefix with - for descending.
Comma-separated response fields to include.
Response fields
keystringThe permission key, such as workflow:run. Roles, API keys, and the effective permissions of a member name permissions by key.
namestringThe permission's display name.
areastringThe part of MindCloud it governs: the key before its first colon, such as workflow or member.
assignableToCustomRolesbooleanTrue when a custom role may carry it (Create Role, Update Role).
ownerOnlybooleanTrue when only the built-in Owner role holds it; no custom role may carry it.
apiKeyGrantablebooleanTrue when an API key may hold it (Create API Key).