Skip to main content
PUT
Update Access Profile

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string
required

The ID of the access profile to update.

Body

application/json
name
string

Updated name. Omit or set to "" to leave unchanged.

description
string | null

Updated description. Omit to leave unchanged; set to "" to clear.

matchingCriteria
matching_criteria · object

Which users this profile applies to. Each child present replaces that criterion wholesale; a child omitted is left unchanged. Sending the message with neither child, or an update that would leave the profile with no criterion at all (which would match every user), is rejected.

grants
grants · object
deprecated

Deprecated: manage grants through the access-profile-grant endpoints (/v2/access-profile-grants), which edit one edge at a time instead of replacing the full set. Still honored (replace-all semantics) for compatibility until writes are rejected.

scopedId
string | null

Rekeys the profile's stable identity (apr_ + 22 base62 chars). Omit to leave unchanged. Must be unique within the team. Built-in profiles cannot be rekeyed, and reserved sentinel values are rejected.

Response

200 - application/json

Success

data
data · object

An access profile defines which entitlements are available to which groups of users, and which workflows apply.