Getting started

This page walks a workspace member through picking the right workspace, adding an environment, and linking it to Performance. No org admin powers required.

What you will need

Need Notes
Spanline account app.spanline.dev
Workspace membership At least Viewer; Admin to manage members/environments
Optional: Performance scenario Performance getting started

Step 1 — Select the workspace

  1. Sign in at app.spanline.dev.
  2. Use the workspace switcher in the header (organization name / workspace name).
  3. Pick the workspace your team uses (for example Default).

Everything in Dashboard, Capture, and Performance now reads and writes this workspace’s data.

If you only see one workspace, the switcher still shows the name — you are already scoped correctly.

Step 2 — Confirm on the Dashboard

Open Dashboard (/). You should see:

Dashboard showing workspace-scoped KPIs
Dashboard — confirm the header workspace name before creating inboxes or runs.

Step 3 — Create an environment

Environments hold base URLs and secrets scenarios reference.

  1. Open Workspace → Environments (/workspaces/environments).
  2. Click New environment — name it (for example staging).
  3. Open the environment row → add variables:
    - Plain values for URLs and IDs
    - Secret for API keys (stored sealed; shown as •••• after save)
  4. Optionally mark one environment as Default.

See Guides → Environments for the variables drawer.

Environments list in the workspace
Environments — create staging, production, or other named sets your scenarios reference.
Environment variables drawer with plain and secret fields
Variables drawer — plain values for URLs; **Secret** for API keys sealed at save.

Step 4 — Use the environment in Performance

  1. Open Performance → Scenarios → create or edit a scenario.
  2. Attach your environment in the scenario editor.
  3. Run from the CLI — Performance → Run tests.

Step 5 — CLI and multiple workspaces

If your account has more than one workspace, set an explicit target before running tests:

spanline auth workspace list
spanline auth workspace use <workspace-name-or-id>

Or set SPANLINE_WORKSPACE in CI. See FAQ → CLI picks the wrong workspace.

Next steps