Update Pathway Access

Creates or updates explicit access grants on a pathway. The body is an access-configuration document whose attributes.assignments lists the grants to upsert: each names a principal (principal-type user or group, principal-id, and optionally principal-id-type to identify a user by email or employee-id, or a group by group-external-id) and the access-level to hold (view, update, manage or full-control). A principal that already has a grant is moved to the new level; principals not listed are left untouched; the request is idempotent. Per-principal problems (unknown principal, invalid level) do not fail the request: the valid subset is applied and every principal's outcome is reported in meta.results, with meta.status successful or completed-with-errors. The data array holds the assignments that were applied. The pathway's author and the All Members group hold ordinary grants and are moved like any other principal.

Required Scope

pathways:write

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The pathway id.

Body Params

An access-configuration document. data.id is optional and must equal the id in the URL when present. assignments holds 1 to 1000 items.

data
object
required
Responses

500

The engine could not decide or apply the change for the resource (write-failed); nothing was applied. Retrying is safe.

503

Access configuration is temporarily unavailable (access-configuration-unavailable): the organization's ReBAC rollout mode could not be read, or the
deployment has no ReBAC engine (the detail says which). Retry later.

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json