Skip to main content
POST
Seating adds an existing user account on this deployment to your organisation with the specified role. A signed-in human session with the member.invite permission is required; API keys are rejected with 403 Forbidden to prevent permanent privilege escalation via leaked service credentials. This operation requires the account to already exist on the cluster; it does not issue invitation emails or create new user accounts.
string
required
The email address of an existing deployment account to seat in the organisation.
string
default:"normal"
The role to assign. Must be one of owner, admin, editor, normal, or dataset_operator. You cannot grant a role higher than your own.

Response

string
required
The member’s account identifier (UUID).
string
required
The display name of the member.
string
required
The registered email address.
string
required
Assigned permission role.
string
required
Account status (active).
string
required
When the membership was granted, ISO 8601 in UTC.
Last modified on September 27, 2026