Service accounts
Non-human users that let an integration reach the Birdie MCP Server with an API key.
Overview
A service account is a user of your organization that is not a person. An integration uses it, such as a shared AI assistant, an internal agent or an automation, to reach the Birdie MCP Server with an API key instead of somebody's sign-in.
Because it does not belong to a person, it keeps working when somebody leaves the company, logs out or changes role. Each key can expire after 30, 90 or 365 days, or never, whichever you ask for.
Read Users first for the core concepts behind roles and workspace permissions. A service account follows the same rules.
Requesting a service account
Service accounts and their keys are created by Birdie. Ask your Birdie contact, and tell them:
What it is for, for example "the data team's Claude Desktop" or "our support agent".
Who is responsible for it. This is the person to ask before its keys are revoked.
What it should see. Pick one:
A role across the organization, with that role's access everywhere.
A role on one workspace, which sees only that workspace.
Access groups, which see every workspace those groups grant.
An existing user, which sees exactly what that user can.
How long each key should last: never expire, or 30, 90 or 365 days.
How Birdie creates it
These screens are in Settings → Service accounts, which only Birdie staff can open. They show what happens with the details you send.
Your Birdie contact opens the page for your organization and clicks New service account.

The form asks for the details above: a name, a description, the owner's email and its access.


The new service account appears in the list as Active, with its owner and creation date.

API keys
Each service account can have several keys. Ask for one key per client or team, so one can be revoked without breaking the others.
A key is shown once, when it is created. Birdie stores only a fingerprint of it and cannot show it again, so keep it in a password manager or secret store. If it is lost, ask for a new one.
A key stops working when it expires, when Birdie revokes it, or when its service account is disabled. This takes effect on the next request.
How Birdie creates and revokes a key
Each key has a name and an expiry.

The key is shown once, when it is created. This is the moment your Birdie contact copies it to send to you.

Revoking a key asks for confirmation. Anything using the key loses access on its next request.

A revoked key stays in the list as Revoked, and the others keep working.

To connect a client with a key, see Connect with an API key.
Service accounts on the Users page
Every service account appears in Settings → Users with a Service account tag. Use the User type filter to show only People or only Service accounts.

From there you manage it like any user:
Change its role or workspaces. The change applies to every key it holds.
Block it to stop its keys. This takes effect within 5 minutes.
Remove it to stop its keys for good. This also takes effect within 5 minutes and cannot be undone.
To stop a key at once, or to stop one key while keeping the others, ask your Birdie contact to revoke it or to disable the service account.
What a service account can do
It reads what its access allows, exactly like a user with the same role and workspaces, and nothing more.
It writes only where your organization has enabled writing, the same as for your users. For example, it can draft a coaching note or open an initiative.
It cannot sign in to the Birdie app. It has no password and receives no invite. The exception is one created from an existing user, which keeps that user's own sign-in.
Last updated