Agent Seats
An agent seat is a machine identity on your Alium team — a non-human account that an integration connects through. Every API key, firehose webhook, and OAuth app connection belongs to an agent seat rather than to a person, so your integrations keep running as team members come and go. Nothing breaks when the admin who set it up leaves.
One agent seat is one integration. Every seat has a kind, and holds exactly one credential of that kind. Two integrations means two seats.
A customer admin manages seats under Account → Agent Seats.
Kinds of agent seat
| Kind | Use it for | What the seat holds |
|---|---|---|
| API key | Your own code, n8n, or an agent that calls the Alium API or the MCP server with a key | One active API key (alm_…) |
| Firehose webhook | An HTTPS endpoint you control that receives every published transcript | One firehose webhook |
| App connection | OAuth connections such as Zapier or an MCP client like Microsoft Copilot Studio or Agentforce | One connection to one app |
You pick the kind when you create the seat, and it can't be changed afterwards. Name each seat after the integration it's for — hubspot-sync, zapier, copilot-sales-agent — so the Agent Seats page reads as a list of what's plugged into Alium.
When you connect Claude or ChatGPT to Alium as yourself, you authorize with your own account and no agent seat is involved. Seats are for machine integrations — anything that should keep working independently of any one person.
Who can manage seats
Only customer admins can create agent seats, mint or rotate their API keys, and see the Connect as picker on the Alium authorization screen. If you're setting up Zapier or Copilot Studio and don't see a seat to pick, ask a team admin to create an app-connection seat first.
Creating an agent seat
- Go to Account → Agent Seats and click New Agent Seat.
- Choose what the seat is for: API key, Firehose webhook, or App connection.
- Give it a name: 3–30 characters, lowercase letters, digits, and hyphens. The name becomes the seat's identifier,
<name>@agent.alium.io. The seat can't send mail, but anything sent to that address forwards to your team's admins. - Click Create. What happens next depends on the kind:
- API key — the key is minted immediately. Copy it now; the full value is shown only once. See Authentication for how to use it.
- Firehose webhook — you're taken to the new-webhook form with the seat preselected. Enter your endpoint URL to finish. See Webhooks.
- App connection — nothing else to do in Alium. Start the connection from the app's side (Zapier, Copilot Studio, …) and pick this seat under Connect as on the Alium authorization screen.
Plan limits
The number of agent seats depends on your plan. The Agent Seats page shows how many you've used. If your plan doesn't include agent seats, or you've used all of them, contact sales@alium.io to add more.
Rotating and disconnecting
Each kind of seat has one credential, and you manage it from the seat's page:
- API key — Rotate issues a new key and revokes the old one immediately. Anything using the old key fails until you give it the new token. Use this if a key is lost or compromised.
- App connection — Disconnect revokes every token the app holds for this seat. Connected Zaps or agents stop working until you reconnect from the app's side and pick the seat again.
- Firehose webhook — delete it from the Webhooks page, or from the seat's page.
Rate limits apply per agent seat, so a busy integration never slows down another one.
Older seats could hold several integrations at once. Those still work and show a Mixed flag on the Agent Seats page. Contact help@alium.io to split one into one seat per integration — nothing stops working in the meantime.