Workspaces
Workspaces help organizations group related private endpoints and manage access from one place. Create a workspace for a team, project, service, or environment, then add the endpoints and people associated with it. Every endpoint in the workspace follows the same access policy and member permissions, so administrators do not need to manage sharing separately for each endpoint.
Organization administrators create and manage workspaces from Manage Organization > Workspaces. Existing endpoints remain independent until an administrator adds them to a workspace.
Workspaces are available with the Enterprise plan. Only organization administrators can create workspaces or manage their endpoints, members, and settings.
Manage Workspaces
Create a workspace
To create a workspace:
- Open Manage Organization > Workspaces.
- Select Create workspace.
- Enter a unique workspace name and an optional description.
- Choose an access policy:
- Restricted allows only explicitly added workspace members to access its endpoints.
- Organization read-only allows everyone in the organization to view its endpoints. Explicit members can receive Write or Manager access.
- Create the workspace.
Add endpoints
Open the workspace's Endpoints section, select one or more endpoints, and choose Add. You can add private organization endpoints that are not assigned to another workspace. After an endpoint is added, the workspace's access policy and member roles control who can use it. An endpoint in a workspace cannot maintain a separate list of direct collaborators.
When you add an endpoint to a workspace, its previous sharing settings are removed and it will now inherit the workspace’s access policy and permissions.
You can also move endpoints from one workspace to another. The endpoint immediately adopts the destination workspace's access policy and member permissions.
Add members
Open the workspace's Members section and add existing Beeceptor users. You can add multiple users at once and assign a role:
| Role | Access |
|---|---|
| Read | View requests, history, Mock Rules, basic settings, CRUD objects, and state. |
| Write | Read access, plus permission to update Mock Rules and endpoint configuration. |
| Manager | Write access, plus permission to manage endpoint settings, API keys, MCP, and available audit logs. |
To invite a user to a workspace, their Beeceptor account must already exist, and their email address must be from the organization’s primary domain or an approved sharing domain. Any changes to roles or member removals are immediately applied to all endpoints within the workspace.
Delete a worksapce
Before you can delete a workspace, you need to empty it by moving or removing all of its endpoints. Deleting a workspace will remove all member assignments for that workspace but will not delete any endpoints themselves.
Audit: All actions related to workspaces (including creation, settings modifications, endpoint assignments or removals, and membership updates) are automatically logged in the organization’s audit records for full traceability and compliance.
Workspace Managed Endpoints
Independent endpoints use the standard sharing controls and can have their own direct collaborators. However, when an endpoint is moved into a workspace, its sharing is governed by the workspace’s access policy:
- Individual sharing for that endpoint is disabled. Sharing permissions cannot be overridden on a per-endpoint basis within a workspace.
- Only organization administrators can manage workspace memberships, including adding or removing members or changing their roles.
- Each member has the same level of access for all endpoints within the workspace.
- Removing an endpoint from a workspace returns it to independent status, with access restored only to the owner. You will need to add collaborators again if needed.