Settings
Settings sits at the foot of the navigation. It has three tabs: API keys, which only administrators see; Connected apps, where everyone sees the AI assistants they have connected; and Security, which is your own account and is open to everyone.
API keys
Section titled “API keys”A key lets another system — an HR platform, usually — invite people and read their status through the Integration API, without anyone sharing a login.
One key acts for the whole company. There is no per-sphere scope, so a key you issue reaches every sphere you hold.
What a key never returns is the contents of a card: no contact’s name, no phone number, no field value of any kind. It can return a link to where a card lives in the Portal, but a link is an address, not access — following it still requires a signed-in Portal session, and the card is still only shown to somebody whose permission the owner can end.
Issuing one
Section titled “Issuing one”New key, and give it a name. Name it after the system that will use it, not after the person creating it — in a year the name is the only thing telling you what a key is for.
The value carries a recognisable prefix, so if it ever ends up in a code repository, automated secret scanners can spot it.
Living with keys
Section titled “Living with keys”The list identifies a key by its name, its last four characters and its status. That is enough to tell two keys apart without the list being able to reveal either.
Revoking takes effect immediately, and revoking twice is harmless. A revoked key stays in the list: the row is the record that the credential existed at all, and deleting it would be deleting history.
Issuing and revoking both go into the compliance trail, which never records the key itself.
Revoke a key when the system using it is retired, when the person who set it up leaves, or the moment you suspect it has been seen by anyone who shouldn’t have it. There is no cost to issuing a fresh one.
Your API documentation
Section titled “Your API documentation”This tab also carries the links to your company’s own Integration API documentation — the ones you hand to whoever is building the integration.
Those links are private. The key inside the URL is what makes them yours, so treat them the way you would treat a credential: send them directly to the person who needs them, not into a group chat.
Connected apps
Section titled “Connected apps”When somebody connects Claude or ChatGPT by signing in, the connection is listed here: the app, the person, when it was connected, and when it was last used.
Everyone sees their own connections. As an administrator you see everyone’s in the company, and you can disconnect any of them with the bin icon — the assistant stops working at once. Do it when a laptop goes missing or somebody leaves; archiving a person ends their connections too.
A connection is not a key. It acts as one person, with their role and spheres, and lasts at most 90 days before they sign in again. An API key acts for the whole company until you revoke it.
Security
Section titled “Security”The second tab is your own account: your second factor and how many recovery codes you have left.
Everyone on Team can open it — operators as well as administrators. It is about your own sign-in, not about managing anybody. Resetting somebody else’s factor is a different thing and lives on Team, which also covers when using it is appropriate.
What recovery codes are for
Section titled “What recovery codes are for”They are a way in, not a way to repair your second factor. When you cannot produce a code from your authenticator app — the phone is lost, wiped or in somebody else’s hands — a recovery code signs you in that one time instead.
It does not restore the factor and it does not move it to a new phone.
Each code works once. If you run out, or never saved the set you were shown, an administrator can clear your factor from Team and you set it up from scratch on your next sign-in. That is the last resort, not the normal path, and it means somebody has to be sure it is really you asking.