Stepshots logoStepshots

Teams

Share demos, guided tours and sandboxes with your teammates. Create a team, invite members, pick roles, and upload into a team from the CLI with --org.

Overview

Every Stepshots account starts with a personal workspace. A team is a second kind of workspace that several people share: its demos, guided tours, sandboxes, analytics, plan and demo credits belong to the team, not to whoever created them.

Switch between workspaces with the Workspace selector at the top of the dashboard sidebar. Everything you see and create — the demo list, analytics, tours, sandboxes, billing — follows the workspace you're switched to. Switching workspace reloads other open dashboard tabs when you return to them.

Create a Team

  1. Click Create team in the dashboard sidebar (or in Settings → Team).
  2. Enter a name. Stepshots derives a slug from it (e.g. Acme Corp → acme-corp), which is how the CLI and the MCP server refer to the team.
  3. You're switched into the new team as its owner.

Invite Members

In Settings → Team, enter a teammate's email, pick a role, and click Invite. They get an email with a link that is valid for 7 days. Opening it asks them to sign in (or sign up) and then to confirm joining.

  • Re-inviting the same address replaces the earlier invitation and invalidates its link.
  • Pending invitations can be revoked at any time; the emailed link stops working immediately.
  • Each link works once.

Roles

Role Can
Owner Everything below, plus billing (upgrade, cancel, invoices) and transferring ownership. Exactly one per team.
Admin Rename the team, invite and remove members, change roles.
Member Create, edit and publish the team's demos, tours and sandboxes.

To hand a team over, the owner clicks Make owner next to another member; the previous owner becomes an admin. Members other than the owner can Leave team from Settings. To delete your account while you own a team with other members, transfer ownership first. The subscription portal and invoices stay with the person who paid for the plan, since they belong to that person's billing account.

Seats

Seats are counted per team: current members plus open invitations, so a team can't promise more seats than its plan has.

Plan Seats
Free 1 — the owner. A free team can't invite anyone yet.
Pro Up to 5 team members.

The plan is bought by the team owner on the Billing page while switched into the team, and covers every member. Your personal workspace keeps its own plan and is never shared.

Use a Team from the CLI

Uploads go to your personal workspace unless you name a team. Pass its slug with --org:

bash
stepshots upload output/onboarding.stepshot --org acme-corp
stepshots tour push tours/onboarding.tour.json --org acme-corp
stepshots verify --org acme-corp

Or set it once for the project in stepshots.config.json, so CI never forgets it:

json
{
  "organization": "acme-corp"
}

The flag wins over the config value. Commands that address an existing demo by id (upload --demo-id, verify, drift --push) find the demo's team on their own. stepshots whoami lists the teams your token can reach and their slugs.

Your API key stays personal: it works in every team you belong to and stops reaching a team the moment you leave it.

Navigation