Workspaces
What this is
Section titled “What this is”Workspaces are the team boundaries inside a MaxoPerf account. Each workspace is an independent operating slice with its own projects, tests, secrets, members, and private datacenter sites. The Workspaces section lets you create and rename workspaces, inspect workspace identity and access, manage workspace-scoped secrets, and monitor active runs inside a single workspace.
Where to find it
Section titled “Where to find it”- Workspaces list: Left navigation → Account → Workspaces (
/workspaces) - Workspace detail: Workspaces list → click Settings next to a workspace (
/workspaces/:id) - Workspace secrets: Workspace detail → Secrets button, or
/workspaces/:id/secrets - Workspace active runs: Workspace detail → Active runs button, or
/workspaces/:id/active-runs
Workspace list
Section titled “Workspace list”The Workspace directory lists every workspace in the active account. From this view you can create a workspace, rename an existing one, jump to its settings, or scope the console to it.
How to use the workspace list
Section titled “How to use the workspace list”- Navigate to Account → Workspaces in the left nav. The workspace directory loads immediately.
- Create a workspace — click Create workspace in the page header. Enter a name (e.g. “Staging”) in the dialog and click Create. The new workspace becomes the active scope.
- Rename a workspace — click the pencil icon next to the workspace name. Edit inline and press Enter or click the confirm button. The name updates immediately across the console. Only workspace editors and account owners can rename.
- Open workspace settings — click Settings next to the workspace. This opens the Workspace detail page.
- View projects for a workspace — click View projects. The console scopes to that workspace and opens the Projects list.
- Select a workspace for the console scope — use the workspace scope switcher in the top bar rather than this list. Creating a workspace automatically sets it as the active scope.
Workspace detail
Section titled “Workspace detail”The Workspace detail page (/workspaces/:id) is the control plane for a single workspace. It is reached from the Workspaces list by clicking Settings next to any workspace.
Identity section
Section titled “Identity section”The Identity section shows the stable workspace id and the parent account id, both truncated with tooltip copy. It also displays your effective access role (viewer / editor / admin) for this workspace.
Launch control section
Section titled “Launch control section”The Launch control section contains quick-access buttons to the workspace’s most-used objects:
| Button | Destination |
|---|---|
| Projects | Projects list scoped to this workspace |
| Private datacenters | Private datacenters list for this workspace |
| Active runs | Workspace active runs (/workspaces/:id/active-runs) |
| Secrets | Workspace secrets vault (/workspaces/:id/secrets) |
| Notifications | Settings → Notifications |
| All tests | Tests list scoped to this workspace |
Access section
Section titled “Access section”The Access section lists every team that has a grant targeting this workspace, along with the team’s role (viewer, editor, or admin). If no team grants exist, a note says so.
To change workspace access, go to Teams and edit the team’s workspace grants from there.
How to use workspace detail
Section titled “How to use workspace detail”- Open the Workspaces list and click Settings next to the workspace you want to inspect.
- Rename — click the edit icon next to the workspace name in the page header and type the new name. Only editors and owners can rename.
- Copy the workspace id — hover over the truncated id in the Identity section and click to copy. Use this id in API calls or when raising support tickets.
- Navigate to a resource — click any button in the Launch control section to go there directly (the workspace scope is set automatically).
- Review team access — scroll to the Access section to see which teams have which roles on this workspace. Click through to Teams to change grants.
Workspace secrets
Section titled “Workspace secrets”The Workspace secrets vault (/workspaces/:id/secrets) stores encrypted key-value pairs scoped to this workspace. Tests reference secrets by name and the runner injects the value at run time — the raw value is never exposed in the UI after creation.
How to manage workspace secrets
Section titled “How to manage workspace secrets”- Navigate to workspace secrets via Workspace detail → Secrets or directly to
/workspaces/:id/secrets. - Create a secret — click Create secret. Enter a Name (e.g.
STRIPE_SECRET) and a Value in the dialog. Click Save secret. A toast confirms creation. The value is encrypted at rest and will never appear in the UI again. - Rotate a value — click Rotate value next to the secret. Enter the new value and click Save. The version counter increments by one. Existing runs using the previous version continue until they complete; new runs pick up the next version.
- Delete a secret — click Delete and confirm. Any tests currently bound to this secret lose the binding — update the test configuration before deleting a secret that is in active use.
- Reference a secret in a test — bind a secret by name in the test’s configuration (Tests → select a test → Configuration). The runner resolves the name to the encrypted value at run time.
Workspace active runs
Section titled “Workspace active runs”The Workspace active runs page (/workspaces/:id/active-runs) shows every test run currently queued, provisioning, or executing inside this workspace. It refreshes automatically every few seconds.
How to use workspace active runs
Section titled “How to use workspace active runs”- Navigate via Workspace detail → Active runs or directly to
/workspaces/:id/active-runs. - The live table loads immediately. Rows refresh every few seconds — no manual reload needed.
- Click a run row to open the Run detail page for real-time Logs and Metrics.
- To monitor runs across all workspaces, use Account → Active runs instead (requires account owner).
Tips & gotchas
Section titled “Tips & gotchas”- Workspace scope follows the switcher. The workspace selected in the top-bar scope switcher controls what the Dashboard, Runs list, and Secrets nav link show. Navigating to Workspace detail from the list sets the scope to that workspace automatically.
- Secrets are workspace-scoped, not account-wide. A secret created in workspace A is not visible to tests in workspace B. Use the account-wide Secrets hub for cross-workspace keys.
- Name changes propagate immediately. Renaming a workspace updates its name in the scope switcher, the breadcrumbs, and the Workspaces list right away — no refresh needed.
- Delete a secret only when safe. Deleting a secret breaks any test currently configured to use it. Rotate the value instead if you need to change the credential.
- Active runs filter. Workspace active runs only shows in-flight runs. Completed or failed runs are in the full Runs list.
Related docs
Section titled “Related docs”- Accounts, workspaces, and projects — the hierarchy: account → workspace → project → test.
- Account overview & active runs — account-level overview and cross-workspace active runs monitor.
- Teams — manage team workspace access grants.
- Members & invites — invite and manage account members.
- Secrets — account-wide secrets hub (cross-workspace).
- Runs — read results — read Metrics, Logs, and Artifacts for a finished or live run.