Workspaces
How workspaces, team members, and project access work in Smoketest.
A workspace is the top-level container for everything in your Smoketest account — projects, billing, and team members.
Your workspace
When you sign up, Smoketest creates one workspace for your account. All projects you create live inside this workspace and share the same credit balance and billing plan.
What's in a workspace
| What | Description |
|---|---|
| Projects | All projects belong to your workspace |
| Billing | Your plan, credit balance, and boost packs are workspace-level |
| Members | Organization roles and project/source assignments |
Workspace settings
You can find workspace settings by clicking your workspace name in the sidebar → Settings. From there you can:
- Rename the workspace
- Manage billing and view credit usage
- View your current plan
- Invite teammates and manage their project access
Team collaboration
Each member has one organization role:
| Role | Access |
|---|---|
| Owner | Organization creator with full access, including billing. Cannot be removed or demoted by another member. |
| Admin | Manages all projects, sources, integrations, invitations, and member access, including other Admins. Cannot change the Owner or manage billing. |
| Tester | Authors and runs reusable Tests, shared steps, tags, schedules, and environments in assigned projects. Operates assigned Test Sources. |
| Viewer | Reads assigned project resources and source evidence. Cannot change testing resources or trigger Runs. |
Owner/Admin can invite teammates from Settings → Team. New invitations default to Viewer with no project assignments. Links expire after seven days and must be accepted using the invited email address.
Projects are assigned separately from the role. Each assignment includes All sources, including future sources, or Selected sources. Selecting no sources still gives access to shared reusable Tests, environments, and their Runs. Owner/Admin always have all projects and sources.
Testers with all-source access can create a Test Source using an existing Connection. Testers assigned selected sources can edit their configuration, pause, reactivate, and archive them, but cannot change their Connection, board, team, or provider project. Only Owner/Admin administer Connections and integrations.
Shared environments are available throughout a project; editing one can affect sources you cannot otherwise access. Saving a generated Test as reusable creates a shared project copy. Source assignments restrict source-generated evidence, Board, Overview, Analytics, and individual email results, including digests.
Every member can manage personal notification preferences and credentials. API, CLI, and MCP credentials inherit the creator's current role and assignments, limited by their scopes. Viewers can create read-only credentials. Removing a member revokes their access; changing assignments also applies to subsequent credential requests.
Switching workspaces
If you belong to multiple workspaces, use the project selector to switch between their projects. Selecting a project in another workspace also changes your active workspace.
Organizations without assigned projects remain selectable and show an access-pending state. Ask an Owner or Admin to assign a project.