Skip to content

Collaboration Workspaces

Workspaces are used for collaboration between testers. A workspace contains several members with a role for each one:

  • At least one Admin (he can add other members and edit the workspace),
  • Testers can create new projects,
  • Viewers can check the Virtual Users and test results,
  • Test Executors can do anything in the project, except edit the virtual users.

All members of a Workspace can utilize the resources of the Workspace - be it Virtual users, Tests Reports, Scenario configuration, private injectors etc.

Workspaces are a good way to have different groups of users work in isolation. While at the same time sharing some resources, like private injectors.

Here is an example of what you can achieve:


Typically is an administrator, he doesn't have any project of its own. But he created a workspace to share access to a group of On-Premise Agents with others workspaces. That way, he is the only one to be able to edit the provider, even if other workspaces have a local administrator in them. On the other hand only has specific access to one project only ; probably read only but not necessarily.

Workspaces Administration

Workspace Menu

The workspaces can be accessed from the left menu. This will open the workspace list.


A simple click on any workspace will open it and go to the list of projects, other actions are available:

Icon Action Description
workspace-create-new Create new workspace This will create a new workspace with your account as its single admin.
workspace-edit Edit Workspace Opens the edition panel to let you change the workspace name, its description and members.
workspace-delete Delete Workspace Lets you remove a Workspace in one click. All the projects of the workspace are also removed. This operation cannot be reverted so proceed with caution.


The search functions are detailed in this section of the navigation page.

Create a workspace

When you click on create a new workspace, you will be prompted with this menu:


The new workspace will then be highlighted in the list:


Edit a workspace

Edit Workspace

This screen allows you to edit the workspace name and description but also Add/Edit/remove members. The filters on the members list work similarly to the ones on the workspace list.


To open this screen you must have administrator rights on the workspace, otherwise you'll get a 403 error: not-admin-error

Members panel

Icon Description
workspace-create-new-member This will add a new member. You must enter a valid login from an existing OctoPerf user.
workspace-delete Remove the member from this workspace.


The workspace must have an administrator, if you try to remove the last administrator you will get an error message: last-admin-error

Edit a member

Members can have different roles:

  • Admin can add other members and edit the workspace,
  • Testers can create new projects and access everything inside existing ones,
  • Viewers cannot edit anything but can see all virtual users and reports,
  • Test Executors can do anything in the project, except edit the virtual users.

On top of that it is possible to give advanced rights on a project per project basis:


The Advanced role allows you to give access only to specific Projects and Providers. You can add as many specific authorizations as you need but if new projects are created later in this workspace you will have to update the rights so that this user sees them. For this reason we recommend to use one of the predefined roles above.

Remove a workspace

Removing a workspace deletes all the objects it contains - projects, virtual users, scenarios, monitored machines, test reports, private injectors etc.


For that reason, deletion of a workspace is strictly restricted to platform administrators only!

When using the SaaS edition to have a workspace removed you must:

  • add as admin of the workspace,
  • send a mail to our Support Team to ask for this workspace to be removed,
  • if we can confirm that you are administrator of this workspace, we will remove it and notify you.


Every user must have at least one Workspace. A default one is automatically created during connection if there is none.