Create User

POST /users

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Request body — UserCreate

Field	Type		Notes
email	string	required	min length 3 max length 254
full_name	string | null	optional	max length 200
password	string | null	optional	min length 12 max length 256
role	viewer | member | admin | owner | operator	optional	Default "member".
scope	workspace | organization | platform	optional	Default "workspace".
workspace_id	string (uuid) | null	optional	—

Responses

Status	Description	Body
201	Successful Response	UserView
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X POST https://your-deployment.example.com/users \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "email": "string"
     }'

Response — UserView

Field	Type		Notes
id	string (uuid)	required	—
email	string	required	—
full_name	string | null	optional	—
role	viewer | member | admin | owner | operator	required	—
scope	workspace | organization | platform	required	—
organization_id	string (uuid) | null	optional	—
workspace_id	string (uuid) | null	optional	—
is_active	boolean	required	—
mfa_enabled	boolean	required	—
last_login_at	string (date-time) | null	optional	—
created_at	string (date-time)	required	—
updated_at	string (date-time)	required	—