Users

GET works with READ. Creating, updating, or deleting users requires WRITE (Authentication & scopes).

What you get

User payloads include identity, contact, and HR-style profile fields, plus a role (EMPLOYEE or ADMIN) that controls Fleet permissions.

Listing

The list endpoint is paginated. Use limit and offset for pagination.

Creating and updating

Create requires a valid work email and optional profile fields. Fleet enforces email policy and uniqueness.

Update supports profile data, role, and email changes where allowed. For each field, follow the schema for omit vs null behavior.

Relationship to carts and devices

User IDs are reused across other resources:

• purchaser and signatory in carts/orders
• assignee on devices
• user_id in cart line items

Next steps

• Carts & orders — purchasers and signatories.
• Devices — assignment targets.
• API reference — Users tag for request/response schemas.