Settings and developer access

What each Settings page holds, and how to connect an agent and create, replace and revoke API keys and authorized apps.

Open Settings from the account menu at the bottom of the sidebar, or press G then S. Press / to search Settings. It opens on General and shows the workspace you are in. To change another, switch to it from the account menu first.

Settings pages

  • General: the workspace's name and address. Admins can change the name, and the address once.
  • Members: the organization's members, their roles and Pending invites. Personal workspaces don't have it. See Invite members.
  • Repositories: where you add and manage repositories, a section per source. In GitHub, you install the V12 GitHub App and add the repositories it can access, or public ones; see Connect GitHub. In Hosted by V12, an Admin creates a repository V12 hosts with New repository and gets its push URL from Push on its row; see Hosted repositories. In your personal workspace, Shared with you lists the repositories other organizations have shared with you, and Open opens their findings.
  • Billing: Credit with the Monthly limit, Purchases with their invoices, and Usage. See Credits and billing.
  • Developer: Connect an agent, authorized apps and API keys.
  • Profile: your own account, the same in every workspace: your Username, your email, and Connected accounts, where you Connect or Disconnect GitHub.

In an organization, Profile is listed under Account. A personal workspace has no separate Profile: its General page holds your profile and the workspace's Address.

Username

Teammates see your username on findings you own, in Activity, in assignment menus and filters, and in the member list. It starts as your GitHub login if you sign up with GitHub, otherwise as the part of your email before the @. Change it under Profile.

  • A username is 3 to 39 lowercase letters, digits and single hyphens, with at least one letter.
  • Names that could pass for V12 or a system label, such as v12, admin or unassigned, are reserved.
  • Usernames needn't be unique. Where two people in a workspace have names that read alike, teammates see each one's email beside it.
  • A new username renames your personal workspace but keeps its address.
  • Guests, on a shared repository or a guest link, see members by username only, and are marked guest in the organization's Activity.

Connect an agent

Connect an agent is the first section of Developer. It holds what an AI agent needs to use V12's MCP server:

  • Prompt for your agent: paste it into Claude Code, Cursor, Codex or any agent that can add an MCP server. The agent adds V12 to itself and tells you when to approve V12's consent page in your browser. The prompt holds no API key.
  • Server URL: copy it into a client that adds a connector by URL, such as the Claude app or ChatGPT.
  • Setup guide opens Connect an MCP client, with the steps for each client.

Once you approve the connection, the agent appears under Authorized apps.

API keys

An API key lets a script, a CI job or another tool call the V12 API as you.

  • A key works only in the workspace that is active when you create it. To make one for another workspace, switch to it first. See Which organization a token reads.
  • Admins and Members can both create keys, up to 50 active keys per person in each workspace.
  • The API keys table shows Key (the name), Prefix, Scopes and Last used. In an organization, Admins see every member's keys, with a Created by column. Members see only their own.

Create an API key

Go to Settings → Developer and click Create key.

In the Create a key dialog, name the key, for example "CI gate".

Select at least one scope. Each option shows a label, such as View findings, above its scope, such as findings:read. Create stays disabled until the key has a name and a scope. Scopes lists what each allows.

Click Create. The dialog shows the key and says "This secret is shown once. Copy it now." Copy it into your secret store, then click Done.

Keys start with v12p_. A key created here has no expiry date. It works until:

  • someone revokes it;
  • its creator stops being a member of the workspace;
  • its creator changes or resets their password, which revokes all of that person's keys.

Rename or revoke

Each key's row ends with a menu holding Rename and Revoke.

  • Rename turns the name into a field. Press Enter to save or Escape to cancel. Only the key's creator can rename it.
  • Revoke takes effect at once: the next request with the key gets a 401. Admins can revoke any key in their organization.

You can't change a key's scopes; replace the key instead.

Replace a key

V12 can't rotate a key in place. To swap one without an outage:

  1. Create a new key with the scopes you need.
  2. Update the secret wherever the old key is stored.
  3. Check the new key:
    curl -s -H "Authorization: Bearer $NEW_KEY" https://v12.sh/api/v2/me
    The response names the workspace, with the slug REST paths use, and lists the key's scopes. Any valid key can call it, whatever its scopes, so a 401 means the key is wrong.
  4. Revoke the old key.

Authorized apps

Apps you connect over OAuth, such as an MCP client or the V12 CLI, appear under Authorized apps on the Developer page, which says "No authorized apps." until there is one.

  • The columns are App, Scopes and Last used. In an organization, Admins see every member's apps, with an Authorized by column. Members see only their own.
  • Revoke disconnects an app at once, without confirmation. The page says: "Revoking an app invalidates its tokens immediately." To use it again, authorize it again.

On this page