Getting Started
Welcome to Archibot
Learn what Archibot Console is for, how first sign-in works, and what information is safe to share.
What Archibot Console is for
Archibot Console is the customer-facing place to prepare an account, create workspaces, launch editors, review usage, and get support. Normal customer work should not require service tokens, Kubernetes access, internal service addresses, or platform admin tooling.
Use Console for:
- Account setup and customer onboarding details.
- Inviting users and reviewing customer roles.
- Creating workspaces from approved templates and backups.
- Launching Browser IDE or other editor handoffs.
- Stopping, updating, or deleting customer workspaces.
- Reviewing usage and billing readiness when your role allows it.
How to sign in for the first time
- Open the Console URL provided by ISM.
- Choose Continue with SSO.
- Complete your organization sign-in or invite acceptance flow.
- Return to Console and confirm the navigation matches your role.
- Start from Account Setup if you are a customer admin, or My Workspaces if you are a customer member.
If you land on an access-denied page, sign out of the identity provider and try the Console URL again. If the same problem repeats, send support the company name, your email, the role you expected, and the time of the failed sign-in. Do not send invite tokens or cookies.
What to do next
| Role | First page | Goal |
|---|---|---|
| Customer admin | Account Setup | Confirm company details, SSO status, invites, and readiness. |
| Customer member | My Workspaces | Start or create the workspace assigned to your customer account. |
| Platform operator | Tenant Admin | Review customer setup, billing state, SSO handoff, and support context. |
| Platform admin | License | Review platform-only configuration when required. |
Safe information sharing
Share company contacts, repository locations, backup choices, non-secret identity-provider metadata, role expectations, and visible Console error messages.
Do not share passwords, private keys, API keys, cookies, raw tokens, one-time invite links, webhook secrets, database URLs, payment credentials, kubeconfigs, or screenshots that expose those values.
Quick recovery guide
| Symptom | First action | Escalate with |
|---|---|---|
| Expected page is missing | Sign out and sign in again. | Email, company, expected role, visible navigation. |
| Invite opens access denied | Sign out of the identity provider and reopen the invite. | Invite recipient email and approximate time, not the invite link. |
| Workspace create is blocked | Read the blocker and open the relevant guide. | Workspace target, template, visible blocker, and account name. |
Done When
- You can sign in through the expected identity provider.
- The navigation matches your role.
- You know which page to open next.