Skip to main content
The dashboard supports three sign-in methods. All of them produce a session cookie that lasts 7 days.

​
Email and password

1

Sign up

On the login page, click Create an account. Enter your email and a password. The server verifies email format and minimum password complexity.
2

Sign in

Enter the same email and password. The session cookie is set on success.
3

Choose how to get started

Signup does not create an org for you. On first sign-in you land on /onboarding with three choices: Personal account (one click — creates a personal workspace with a default profile, ready to store secrets immediately), Create a new organization (for a team you’ll own), or Join with an invite (paste an abi_… code or invite link). A personal account presents as a personal account rather than an org, holds one profile by default, and can register many agents — and you can still create or join team orgs later from the org switcher.

​
Google or GitHub

If your deployment has the OAuth providers configured, the login page shows Sign in with Google and Sign in with GitHub buttons.
1

Click the provider button

The browser is redirected to the provider’s consent screen.
2

Approve

Approve the abadge app’s requested scopes (email and profile).
3

Choose how to get started

On first sign-in you land on /onboarding and pick Personal account, Create a new organization, or Join with an invite (same as the email/password flow above). Subsequent sign-ins go straight to the dashboard.

​
Approving a CLI device code

The CLI uses a device authorization flow. When abadge login runs, it prints a user code and a verification URL.
1

Open the verification URL

The CLI tries to open it for you. Otherwise, paste it into a browser. You can also go to /device and type the code manually.
2

Sign in if needed

If you’re not already signed in to the dashboard, complete the sign-in flow first. You must have at least one organization before you can approve a device.
3

Confirm the user code

The dashboard shows the user code from your CLI and a countdown (codes expire after 15 minutes). Confirm that it matches before approving.
4

Click Approve

The CLI’s device-code poll succeeds within a few seconds. Your CLI is now attached. Deny rejects the request instead.
Only approve a device code that you initiated. If a verification page appears unexpectedly, deny it and rotate any agents that may have been provisioned during a stolen session.

​
Sessions

​
Multi-factor authentication

Not in v1. Use a strong unique password and rely on your provider’s MFA when signing in via Google or GitHub.