Get Member Permissions

See exactly what one member can do, permission by permission, and why: from their role, a direct grant, or a company setting. It is the answer MindCloud's own authorization gives.

GET

Path

Path parameters

stringrequired

The member's userId, from List Members.

Headers

Optional headers

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.

Response fields

userIdstring

The member's userId.

roleIdstring

The role they hold in the company.

permissionsarray of objects

Their effective permissions, in key order.

keystring
The permission key, from List Permissions.
namestring
The permission's display name.
sourcesarray
Where it comes from: role, directGrant (granted to the person outside any role), staff (their MindCloud staff role, which replaces a company role), companySetting (the jobs screen setting), or membership (every member holds it, as analytics:page:view). A permission held two ways names both.