Skip to content

Dashboard tour

The dashboard is served by the same Worker as the API, at the instance’s root URL. It uses the same session and permissions as the API: a page or a button you are not allowed to use is hidden or disabled, and the server rejects the request anyway.

  • /setup appears only on a fresh instance. The first account created there becomes the owner; do it right after the deploy.
  • /login, /accept-invite and /reset-password are the sign-in page and the landing pages of invite and password-reset links.
  • Projects (home) lists the projects you can access. Instance owners and admins can create one.
  • Project overview shows, for one folder at a time, which subfolders and keys exist in which environment: a check where it exists, Missing where it does not. Subfolders come first; click one to open it, and use the path at the top right to go back up. No values are shown.
  • Environment (/projects/<project>/environments/<env>) is where secrets live:
    • The sidebar’s environment switcher changes the environment for the whole project.
    • The table lists the secrets of the current folder in columns: Key, Value (masked), Comment, Version and Updated. A long comment is cut to one line; hover it to read it in full. Reveal and copy appear on hover; the row’s ⋮ menu also has Copy key and Copy value. Create and edit open a side sheet.
    • The side sheet has a Type (Text, Number, Boolean, JSON, List, PEM; stored as string, number, boolean, json, list, pem) and a Sensitive switch (on by default). Each type has its own editor: true/false buttons for Boolean, a Format button for JSON, one row per item for List (stored as a JSON array of strings), and Load from file for PEM. The value is checked against its type once you leave the field and again on save; the reason (for example not valid JSON at line 2, column 8) shows under Value. When you edit a secret, the value stays unchanged unless you choose Reveal current value or Replace value. A secret whose type is not string carries a type tag next to its key. Values of non-sensitive secrets are plain config: the table shows them as stored, without a reveal button.
    • Folders: browse with the path breadcrumb, Create folder, Delete folder.
    • Imports: Add import shows another folder’s secrets here; imported rows carry an Imported from label. See References and imports.
    • A value with references shows both the stored value and the Resolved value.
    • The row menu has History (versions, reveal a past value, Roll back). See Versions and rollback.
  • Environments: create, rename and delete environments.
  • Members: add instance users to the project, set their role (admin, developer, viewer) and the environments they may access.
  • Service tokens: create (the token is shown once), list with last use, revoke. Expires in offers 7, 30, 90 (default) or 365 days, or No expiry for a token that stays valid until revoked; the list shows Never for it. See Use Anchor in CI.
  • Encryption: the project key versions and rotation status; start a rotation. See Rotate a project key.
  • Users: invite people (a link valid 72 hours), change instance roles, disable or delete accounts, create password-reset links. The last active owner cannot be demoted, disabled or deleted.
  • Audit log: the instance audit log, filterable by project, actor and action, with each event’s target and metadata. Project admins who are not instance admins get Project audit log in the sidebar instead, for their project.
  • Change your password.
  • See your active sessions (dashboard and CLI) and revoke any of them.
  • Connected apps: the AI agents and apps you approved over OAuth (see Connect AI agents over MCP), with their permissions (Read, Write, Reveal), when you approved them and when they were last used. Revoke cuts an app off at its next request.

When an MCP client such as Claude Code or Codex connects, your browser opens /oauth/authorize (sign in first if asked). The page names the app and the host it returns to, and lists what it will be able to do: see your projects, secrets and non-sensitive values, and create, change and delete secrets. If the app asked to read sensitive values, an Also allow reading sensitive values checkbox appears, unticked; leave it unticked unless the agent needs secret values in its context. Only approve if you just connected an AI agent or app to Anchor. Either button sends you back to the app. Only a dashboard session can approve.

anchor login opens /cli/login in your browser (sign in first if asked) and prints a code. Type the code from your terminal yourself (never one someone sent you) and press Continue. The page then shows the code in large type, the device name the CLI sent, the IP address and how long ago the request was made. Only approve if you just ran anchor login and this code matches your terminal. Approve gives that terminal a CLI session as you (30 days, revocable from your sessions list); Deny makes the CLI stop with “Login was denied in the browser”. Either way the page then says “You can close this tab and return to your terminal.”

Opened without a code (or with a malformed one), the page asks for it; spaces, dashes and case do not matter (wdjb mjht works). A code that expired after 10 minutes or was already used shows “This login request expired or was already used.” Only a dashboard session can approve; a CLI session or service token cannot.