Subscribe and get access
This page is the customer-facing path from “I want AtlasAI” to a signed-in tenant and the onboarding checklist. For day-to-day sign-in, SSO, and password reset, see Authentication & user management.
1. Subscribe (shared SaaS)
- Open the marketing site (e.g. atlastechlab.com ) and choose Get started / Sign up.
- Enter your work email, name, and organization. Submit the form.
- Verify your email when you receive the message (if verification is enabled for your environment).
- Choose a plan and complete checkout if billing is required (Stripe / Razorpay, depending on configuration).
- Wait for provisioning to finish. The platform creates your tenant, applies quotas, and prepares your workspace. A welcome email is sent when the tenant is ready.
Your Tenant Plane URL almost always follows this pattern:
https://<your-tenant-slug>.atlastechlab.comThe slug is derived from your organization (often from the email domain). If your deployment uses a dedicated or on-prem Tenant Plane, the welcome email uses your endpoint_url instead—bookmark that URL only.
More detail: Shared SaaS setup · Technical DNS and automation: see the engineering doc URL automation & auth wiring in the product repository (docs/URL_AUTOMATION_AND_AUTH_WIRING.md).
2. First sign-in (get access)
How you authenticate depends on how the tenant was created:
| Path | What you do |
|---|---|
| Welcome link (recommended) | Open the link from the welcome email. It may include a signup token. Complete set password on the Tenant Plane; the app calls /api/auth/signup-exchange to create your admin user and issue a session. |
| SSO | If your admin enabled SAML/OIDC, use Sign in with SSO on the login page. |
| First user only (empty tenant) | In some dev or greenfield tenants, /api/auth/register can create the first admin when no users exist yet. If the tenant already has users, registration is closed—use invite or signup token instead. |
Control Plane vs Tenant Plane
- Tenant Plane — where your team works (incidents, runbooks, settings). This is what you get after subscribe.
- Control Plane — platform operator console (all tenants). Subscribers normally do not use CP for daily work. See Getting started overview and your operator runbook for CP URLs.
3. In-product onboarding
After you can sign in:
- Open Onboarding (guided setup), usually at
/onboarding, if your tenant shows it. - Complete steps such as connecting data, vault, or integrations—the exact steps depend on your plan and admin configuration.
- Use Settings to finish users, API keys, and SSO.
Progress is stored per tenant via the onboarding API (GET / POST / PATCH /api/onboarding on the Tenant Plane).
4. Demo environments (lab only)
Some demo stacks enable a pre-seeded Tenant Plane login for walkthroughs (not for production customer identity). If your operator confirms demo login is enabled, documentation for those accounts lives with your deployment spec. Do not reuse demo passwords in production; disable demo flags when the environment goes live.
5. Next steps
- Users, roles & access — Invite, SSO/SCIM, roles, Settings (step-by-step).
- Self-service portal — Requester journey: catalog, requests, knowledge.
- Workflows (ITSM vs automation) — Two workflow types; catalog
workflow_definition_id. - Authentication & user management — Invites, forgot password, SSO, user list.
- Edge Agent installation — Install collectors after you have a tenant URL and credentials.
- Your first incident — Validate the workspace end-to-end.
This page ships with the docs portal (apps/docs). Updating it requires rebuilding and redeploying that site so docs.<your-domain> serves the new content.