Skip to content
OttoTester docs

Set up a workspace

Where a workspace sits

Section titled “Where a workspace sits”

A workspace is where a team’s work lives — its applications, variants, tests, and runs. It belongs to an organization:

Organization → Workspace → Application → Variant

Most organizations have a few workspaces — one per product line, say, or one per client.

1. Create the workspace

Section titled “1. Create the workspace”

In Settings → Organization → Workspaces, create a workspace and give it a name. Whoever creates it becomes its first admin automatically. (You need an org-tier role of owner, admin, or member to create one.)

2. Add your teammates

Section titled “2. Add your teammates”

Workspace access is granted per workspace. Open the workspace’s Members & teams settings, add a teammate, and choose their role.

A workspace member must already belong to the organization. If the person isn’t in the org yet, invite them at the org level first (Settings → Organization → Members) — that’s a separate, email-based invite.

3. Pick the right role

Section titled “3. Pick the right role”

Each workspace member has exactly one of three roles:

  • Admin — full control of the workspace: its settings, its members, its applications and variants, and every test.
  • Tester — the working role. Creates and runs tests, edits applications and variants, manages test data and credentials. Can’t change workspace settings or membership.
  • Reviewer — read-only. Sees applications, variants, runs, and reports, but changes nothing.

Pick the least role that lets someone do their job: reviewer for stakeholders who just watch results, tester for everyone doing the testing, admin for the one or two people running the workspace.

Changing a role or removing a member happens from the same Members & teams settings. A workspace must always keep at least one admin — OttoTester won’t let you remove the last one.

Notifications

Section titled “Notifications”

Per-account email preferences live at Settings → Account → Notifications, where each member can opt in or mute their own copies of OttoTester’s run-event emails (run completed, run failed, newly failing tests, etc.). For completed runs, the email includes a PDF report of the run — useful for stakeholders who don’t log into OttoTester.

Slack notifications use the workspace’s Slack connection, configured from Settings → Workspace → Integrations. Pick which Slack channel each application uses on the application’s own Integrations tab; per-variant overrides live in the Slack card’s per-variant drawer on that same tab.

Section titled “Related”