Users
In Settings › Users, admins choose Invite user, enter an Email and pick a Role. The person gets an invitation email and joins when they accept. A pending invitation can be revoked, which stops its link working.
Members can see the Users, API keys and Alerts settings, read-only. Integrations, Billing and Audit logs are admin-only. To change someone’s role or status, use Edit; to remove them, Delete user.
Two kinds of key
Use the agent key in your application’s client or the Xenovia SDK, and the organization key in scripts, CI and integrations that call the management API. The two aren’t interchangeable: the management API rejects agent keys, and the runtime rejects organization keys.
Agent keys
On the agent’s API keys tab, choose Create API key and give it a Key name. Copy the key: it is shown once. Revoke stops a key at once; the runtime rejects a revoked key within seconds. A coding agent’s key is marked Hooks only: it works only on Xenovia’s hook endpoints (see Coding agents). An inline sub-agent has its own keys (see Sub-agents).Organization keys
1
Create it
In Settings › API keys, choose Create API key. Give it a Key label, choose Expires after (30, 60 or 90 days) and Access: Read only or Read and write.
2
Copy it
Copy the secret. It is shown once; the list afterwards shows only the identifier (
ak_…).Handling keys safely
- Store keys in a secret manager and inject them at runtime; never commit them.
- Use separate organizations or at least separate keys per environment.
- Prefer
readkeys for reporting and dashboards; reservewritekeys for provisioning. - Rotate before the expiry date: create the replacement, deploy it, then revoke the old key.
What next?
Audit logs
See who changed what.
API
Use an organization key with the management API.
Create an agent
Make an agent and its key.