Skip to Content
User JourneysFirst Login to First Value

User Journey: First Login to First Value

This journey is for new users and tenant admins: what to do from first sign-in to seeing real value (e.g. your first incident resolved or first dashboard).

Overview

Sign in → Command Center (home) → Optional: connect data → First incident or first dashboard → Value

Step 1: Sign in to the Tenant Plane

Where you sign in:

  • Shared SaaS: Use the link from your welcome email (e.g. https://<tenant>.app.atlastechlab.com/login) or your organization’s bookmark.
  • On-prem / hybrid: Use the URL your admin provided (e.g. https://atlas.yourcompany.com/login).

Ways to sign in:

  • Email + password — If your admin created your account or you registered as the first user.
  • SSO (SAML or OIDC) — If your org uses Okta, Azure AD, or another IdP; choose “Sign in with SSO” on the login page.
  • Invite link — If an admin invited you, use the link in the email to set your password and then sign in.

First-time setup (first user only):

  • If you’re the first user for this tenant, you may see a Register or Set password flow. Complete it; you become the tenant admin with full rights.
  • See Authentication & user management for details on login, forgot password, and SSO.

Outcome: You’re logged in and land on the Command Center (or your org’s default home).


Step 2: Understand the home screen (Command Center)

The Command Center is your operations home. You’ll see:

  • Pipeline strip — Stages from Connect → Discover → Reconcile → Visualize → Correlate → Diagnose → RCA → Act → Automation → Improve → Value. Each stage links to the page where that work happens.
  • Priority queue / active incidents — What needs attention first.
  • KPIs — Connectors, discovery jobs, open incidents, runbooks, automation jobs, etc.
  • Optional: Service map, geographic view, or custom widgets if your admin configured them.

What to do:

  • Click a few pipeline stages to see Integrations, Incidents, Runbooks, Automation. You don’t have to configure anything yet; this is a tour.
  • Tip: Use the command palette (e.g. Cmd+K / Ctrl+K) to jump to any section by name — faster than the sidebar when you know where you’re going. See Using the interface.
  • If you have no data sources yet, the next step is either connecting one (for a full flow) or creating a manual incident to try RCA and runbooks.

Outcome: You know where the main areas live (Data Sources, Incidents, Runbooks, Automation, etc.).


Step 3: Choose your first value path

Pick one to get to “first value” quickly.

Best if you want to see detect → diagnose → act in one go.

  1. Go to Incidents (sidebar or pipeline “Diagnose”).
  2. Click New Incident; create a simple one (e.g. “Test incident – high CPU”).
  3. Add at least one piece of evidence (e.g. a metric or log snippet, or leave minimal for a demo).
  4. Click Run RCA; review the result.
  5. Click Generate Runbook (or pick a template runbook); approve and Execute from Automation.
  6. Resolve the incident.

Result: You’ve closed your first incident with RCA and automation. See Your first incident for the full tutorial.

Path B: First dashboard

Best if you want to see your systems first.

  1. Go to Dashboards (or Service Dashboard / Analytics from the sidebar).
  2. Create a new dashboard; add widgets (e.g. time series, incident list, log stream).
  3. Configure a data source or filter (e.g. by service, environment).
  4. Save and share the link if needed.

Result: You have a live view of metrics, logs, or incidents. See Dashboard design.

Path C: Connect one data source

Best if you want real data before creating incidents.

  1. Go to CONFIGUREIntegrations (or Data Sources / Discovery, depending on your deployment).
  2. Add one connector (e.g. Prometheus, Datadog, or a test Edge Agent).
  3. Confirm data is flowing (metrics or logs).
  4. Optionally run Discovery so services and topology start populating; then open Incidents or Command Center to see how data ties to the pipeline.

Result: Your tenant is ingesting real telemetry; you can then run correlation, create incidents from alerts, or build dashboards.


Step 4: Where to go next

After your first value (first incident, first dashboard, or first data source):


Summary

StepAction
1Sign in (email/password, SSO, or invite link).
2Tour Command Center and pipeline stages.
3Pick one: first incident, first dashboard, or first data source.
4Use User Journeys and User Guide for next steps.

See also