Skip to content
Manybases
esc

Search pages and sections. Try a tool name, an error code, a route.

↑↓ navigate↵ openesc close
  1. Dashboard
  2. Screens
  3. Account
Docs

Dashboard · Screens

Account

Your plan, the key your agent uses to reach every project of this account, the browsers linked to the account, and two-factor authentication. This browser signs in on its own — it never uses your agent key. The GitHub connection lives on Integrations.

Plan#

The plan code, why the account is on it ("default — no subscription yet", "an active subscription", "granted manually"), since when, and the app limit when one was granted specifically.

If the account is above its plan's app limit — after coming back to Free with three projects, say — a notice says since when. Nothing was deleted and nothing stopped: you simply cannot create a new app until you upgrade or remove one.

Legal#

Which version of the Terms of Service this account accepted, and when — or "Not yet" for an account created before the terms were published. Once the legal pages are online, the section links to the Terms of Service and the Privacy Policy, and a new version of the terms asks for your agreement once, the next time you open the dashboard, before anything else.

Agent key#

The account key (ak_) is what your agent uses. An account has at most one live agent key; the card says who holds it: Remote connector (installed from Claude), A local agent (a local MCP server), and its scope — every project, or the projects it was limited to.

  • Generate my account key creates it. Pick its scope first: Every project (required to create new projects) or one project. A key limited to one project cannot create new ones. If the project list could not be read, the key opens every project — reload if you meant to limit it.
  • The value is shown once. Store it in your password manager before continuing — nobody, not even us, can read it back. If you lose it, revoke it and generate a new one. Press "I have saved it — hide it now" when done.
  • It opens every project of this account within its scope, so it belongs in your agent's configuration, never in an app's front end and never in a repository.
  • Revoke cuts the key at the source immediately; anything still using it stops working everywhere within 60 seconds at most. There is no grace period and no way back — you generate a new one. An account has a single agent key, so revoking it here also disconnects anything else that presents it, including an MCP connector.

Two notices can appear instead of the key. "More than one live key, which should not be possible": nothing is broken for your apps, but generate or revoke nothing from here — contact support. "Your keys could not be read just now": this is not the same as having none; do not generate a new one, reload in a moment.

Installing the remote connector revokes the key a local server was using, and vice versa — see Connect an agent.

Browsers#

Each browser you sign in on gets its own key, which never leaves it and is never shown to you. The list shows how many browsers are linked — out of 10 — and which one is this one. Unlinking one frees its slot and cuts its key within 60 seconds at most; it does not sign that browser out of this account, and it does not stop whoever holds it from signing in again. Signing out from a browser releases its slot.

We do not record device names, IP addresses, locations, or when each browser was last used — so this list can tell you how many browsers are linked, not which one is which.

Two situations to know:

  • None of these is the browser you are using right now. This browser is not linked to your account: sign out and sign back in to link it. That will not touch your agent's key, and will not sign out your other devices.
  • All 10 slots are taken. Unlink one before signing in on a new browser — otherwise that sign-in is refused, and the new browser can do nothing about it.

Two-factor authentication#

Off by default. Turned on, every sign-in asks for a 6-digit code sent to your e-mail, after your password. Turning it on asks for a first code to confirm; turning it off asks for confirmation and your password alone signs you in again. There are no backup codes: codes go to this account's e-mail address, and if you lose access to that mailbox you will not be able to sign in — keep that mailbox reachable.