Your account

Profile

Your name — which is how you appear to your team, including on the corrections you make — your email address, and an opt-in for occasional email about new features. The last one is off unless you turn it on, and it has nothing to do with the operational email the product sends you, such as a low-balance alert.

Sign-in methods

You can sign in with a password, with Google, or with both. The rule worth knowing is that the application will not let you remove your last way in:

• A password can only be removed while a connected provider remains.
• A provider can only be disconnected while a password or another provider remains.

So the order matters: add the new method first, then remove the old one. The buttons enforce this, which is more helpful than it is annoying.

Organisations

Every organisation you belong to is listed here, with your role in each, and this is where you switch between them. Switching changes which credit balance your work spends and which workspaces you can see — nothing crosses between organisations.

If a workspace you expected is missing, the first thing to check is which organisation you are currently in; the second is whether a sharing rule reaches you. See also organisation settings.

Personal API keys

Personal API keys live under Integrations → API keys in the app’s settings — one group below Account, with Connections and MCP tools, because all three are ways something outside the app reaches it. A personal key belongs to you within one organisation and reaches every workspace you can reach, which is why it sits with your own account rather than in a workspace. The other kind, a workspace key, belongs to a single workspace and is created from that workspace’s Access tab; see workspaces.

Anyone can hold one. A key never grants more than the person who created it already has, so there is nothing for an admin to gate: if your access is later reduced, every key you hold narrows with it, without anyone editing anything.

You can narrow a key further, workspace by workspace and table by table. A key with no grants on it inherits everything you can reach, which is the useful default and the one surprising thing about the screen — adding your first grant turns the key into an allow-list, so it removes access to everything you did not name. The editor warns you at the moment it happens.

A key is shown once, when it is created, and stored hashed; if you lose it, create another. Revoking one takes up to a minute to take effect everywhere, so a revoked key that still works for a few seconds has not failed to revoke.

What to do with the key is a different question from where to get it, and it has its own section: the API reference covers the endpoints, the header the key goes in, and what each call costs. These docs describe the application.

A connected AI client is not a key, and is not listed here. Connecting one grants access by signing in rather than by issuing a value you hold, so it is listed and withdrawn on its own screen — Integrations → Connections — and revoking a key does nothing to a connection. See connecting an AI client.

Session

Logging out ends the session on the device you are using. It does not sign you out elsewhere, and it does not stop work already running — an extraction runs server-side and finishes whether or not anyone is watching. Closing the tab is not a way to stop a run; stopping it is.