Update Opportunity Access

Creates or updates explicit access grants on an opportunity. 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. Authorship follows the grants: a user given update, manage or full-control becomes an author of the opportunity (as in Manage Access), and a user moved to view stops being one. Group grants do not change authorship. The grants of existing authors and collaborators are moved like any other principal's, with one guard: an item that would leave the opportunity with no user at update, manage or full-control (the user holding the only such grant moved to view, and no other user given one of those levels in the same request) is reported per item as last-author-protected and not applied, while the rest of the request is. Grant another user update, manage or full-control first, or in the same request: the other items are then written first, and the move to view only once one of those users holds the new grant; if none does (for example the promoted user does not exist), the move is reported as last-author-protected next to that item's own failure. The guard looks at the grants as they are when the request arrives. Known limitation: Degreed's author sync cannot remove the last author, so such a user would otherwise stay an author without a grant.

Required Scope

opportunity:write

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

The opportunity id, the id /api/v2/opportunities/{id} uses.

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