Skip to main content

Manage Builder Portal Access

Tasks

Procedures for signing in to the Builder Portal and managing your access tokens, connected accounts, sessions, and policy exceptions.

Accessing the portal​

  1. Go to your workspace URL.
  2. Sign in with your developer credentials. The Builder Portal opens by default — no admin role is required.
note

Admins also have access to the Builder Portal from the same workspace.

Self-registration​

If your organization allows self-registration for your email domain, you can create your own account without an admin invite:

  1. Go to your workspace URL and choose Sign up.
  2. Enter your work email. If it's on an allowed domain, you'll receive a 6-digit verification code by email.
  3. Enter the code along with a password (at least 8 characters) to finish creating your account.
note

Verification codes expire after 10 minutes and allow a limited number of attempts. If you enter the wrong code too many times, wait for the code to expire and request a new one — repeated attempts don't unlock it early.

Access tokens​

Create a token​

  1. Go to Access Tokens and click Create New Token.
  2. Give the token a name that identifies the tool or machine (e.g. claude-code-macbook).
  3. Select an expiry: 30, 60, 90, 180, or 365 days.
  4. Click Create. The token is shown once — copy it immediately. It cannot be retrieved again.
warning

The token value is only shown at creation time. If you lose it, revoke and create a new one.

To revoke a token, click Revoke next to it in the Access Tokens list — it stops working immediately.

Connect your AI tool​

  1. Create a token as described above.
  2. On the Access Tokens tab, copy the ready-to-paste shell command shown for your tool and shell (bash, zsh, fish).
  3. Choose a connection mode: Proxy mode (all LLM and MCP traffic routes through the AIControls proxy) or Passthrough mode (your tool keeps its existing upstream configuration; AIControls intercepts via a lightweight observer).
  4. Run the command in your terminal, then restart your AI tool.

See the Claude Code, Cursor, Codex, or GitHub Copilot pages for tool-specific details.

Sessions and projects​

Sessions and Projects are described in Builder Portal. The one action available here: open a session's detail drawer to end an active or degraded session.

Connected accounts​

Manage a stored credential​

  1. Go to Connected Accounts.
  2. Find the datasource under Stored credentials.
  3. Click Connect (if not yet connected) or Update (to refresh an expired or existing credential).

Configure a client-side credential​

  1. Go to Connected Accounts and find the datasource under Client-configured credentials.
  2. Click View Config to generate the client configuration snippet for that datasource.
  3. Add the header shown to your AI tool's configuration. AIControls does not store these credentials.

Policy exceptions​

  1. Go to Policy Exceptions to view exceptions granted for your identity — operations that would normally be denied by policy but have been explicitly approved, each with an expiry date.
  2. To request a new exception, submit it via the HITL approval flow or contact your admin directly. You cannot create exceptions yourself.

Some requests need more than one approver to sign off before they take effect — see Single- vs multi-approver co-sign. While that's pending, your request shows as Under Review; you'll be notified as soon as it's fully approved or if any approver denies it.

See also​

Last updated on