Account Setup

Customer admin setup

Complete the first account setup pass, submit SSO details safely, invite users, and hand off operator-reviewed items.

Customer adminsPlatform operators
Console-rendered Account Setup page with safe customer details, onboarding checklist, and setup sections.
Console-rendered example with safe data: Account Setup keeps customer-owned details separate from operator-only context and internal notes.

First ten minutes

  1. Open Account Setup.
  2. Confirm the customer name, support contact, billing contact, and technical contact.
  3. Open the onboarding checklist and note any blocked items.
  4. Submit SSO setup details if your team uses an external identity provider.
  5. Invite the first customer members.
  6. Confirm billing or trial approval is visible.
  7. Confirm workspace readiness does not show a hard blocker.

The goal is not to finish every enterprise integration immediately. The goal is to leave enough accurate setup information for the first workspace to be created without repeated back-and-forth.

Submit customer details

Use the customer-owned details form for information your team is comfortable making customer-visible:

  • Legal or operating name.
  • Billing and technical contacts.
  • Repository or artifact notes.
  • AI or workspace preferences.
  • Target launch timing.

Do not put private credentials, payment card details, invite links, or internal-only negotiation notes in this form.

Submit SSO setup details

For OIDC or SAML, provide non-secret metadata:

  • Provider type.
  • Discovery URL or metadata URL.
  • Expected email domains.
  • Username, email, and groups claims.
  • Admin and member groups.
  • Test users for validation.

Do not paste OIDC client secrets, SAML private keys, signing material, passwords, cookies, raw tokens, or one-time links. ISM will use the approved secret exchange path when secret-backed activation is needed.

Invite users

  1. Open the members or invites section.
  2. Enter the user email.
  3. Choose customer admin only for people who should manage setup, invites, and usage.
  4. Choose customer member for ordinary workspace users.
  5. Send or reissue the invite.

If a user opens an invite while already signed into an older or different identity-provider account, they may land on access denied. Ask them to sign out of the identity provider, reopen the invite, and then open Console after acceptance.

Operator-reviewed fields

Some items require ISM review before they become active:

ItemWhy review is needed
Billing stateWorkspace creation may depend on verified, trial-approved, or prepaid status.
External SSO sourceSecret-backed IdP activation must not happen through public notes.
Workspace targetTargets map to runtime capacity, template aliases, and Coder access.
Provider setupManaged AI and customer provider accounts need billing and safety checks.

What to do when setup is blocked

Read the blocker text first. If it mentions billing, prepaid balance, SSO, target readiness, or template availability, retrying Create will not help until that setup gate is fixed.

Send support the customer name, blocked checklist item, visible message, and last action attempted. Do not send secret values or one-time links.

Done When

  • Company and support contacts are current.
  • At least one customer admin can sign in.
  • First customer members are invited or active.
  • SSO details are submitted or marked not required.
  • Billing or trial access is approved.
  • Workspace target readiness is not blocked.