GCgc-ai
Contract Intelligence

Change a member's role

Set a vault member's role.

A vault always keeps at least one owner, so demoting the last one returns 400. Promote another member first, then demote.

The person has to hold a role in the vault already. To grant a first role, use POST /vaults/{id}/members.

Requires the owner role in the vault and the organization-level permission to manage vaults.

Requires a user-scoped API key (u:gcai_...). A vault is shared with named people, so an organization-scoped key has no identity to resolve vault access with.

patch/vaults/{id}/members/{userId}

Request

Path parameters

idstring uuid required

The vault ID

userIdinteger required

GC AI user ID of the member, as user_id from GET /vaults/{id}/members.

Request body

role'owner' | 'editor' | 'viewer' required

The role this member should hold from now on.

Response

The updated vault member

user_idinteger required

GC AI user ID of the member. This is the same identifier GET /me reports for the calling user, so a caller can pick their own row out of the list.

emailstring nullable required

Member email address, or null when the account has none on file.

namestring nullable required

Member display name, preferring the name they chose for themselves. Null when the account has no name on file.

role'owner' | 'editor' | 'viewer' | 'null' nullable required

The member's role in this vault: owner (manage members and settings), editor (add documents and edit extracted data), or viewer (read and annotate). Null on the rare stored value GC AI cannot read as a role. Such a grant carries no permissions at all, so remove it and add the person again.

added_atstring nullable required

ISO 8601 timestamp when the member was added, or null for grants written before GC AI recorded that.

Changes

No recorded changes to this operation across all 1 revision of this API.