Get Member Capabilities

See what Cirra lets one member do (web search, files, shell, and each app) and whether their role, their own choices, or the default decided it.

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 whose rules apply to them.

capabilitiesarray of objects

Every key a layer sets for them, in key order. A key not listed follows its fallback (Get Capability Catalog).

keystring
The capability key, such as files.write or apps.salesforce.contact.update.
valuestring
What Cirra does: allow (asks first unless the thread runs with full access), never_ask (allows without asking), or deny.
- allow
- never_ask
- deny
layerstring
Which layer decided it: default, role, or user (the person's own rules).
- default
- role
- user