Caputchin
Account management

What lives at the account level

Your account is your identity across Caputchin. A few things live at the account level, above any single troop.

Signing in

You sign in by email magic link, GitHub, or Google. Whichever you used first created the account, and any of the three works afterward as long as the email matches. There is no password. Signing out from the dashboard clears the session right away.

Personal access token

For access outside the browser (the API, MCP, or Terraform), your account has one personal access token (cpt_pat_...). It carries your own full access, it is shown once at creation, and you send it as a Bearer token.

Billing and seats

Billing and seats are account-level, not per-troop: one plan covers the account, and seats are shared across all of your troops. See billing for plans, seats, payment, and cancellation.

Settings and traceability

Your email, active sessions, support access, and the account access token are managed on the account settings page. On the Apex plan, audit logs record who changed what across the account, its troops, and its site keys.

See also

  • Account settings for email, sessions, support access, and the account token.
  • Personal access token for reaching Caputchin from the API, MCP, or Terraform.
  • Billing for plans, seats, payment, and invoices.
  • Audit logs for the record of changes on the Apex plan.
  • Troops for the workspaces that hold your site keys.

On this page