Workspaces
Organise team access, services, integrations, and billing within an Openstead workspace.
A workspace is the top-level home for a team's Openstead resources. It contains projects, services, environment groups, member permissions, integrations, and billing records.
Your personal account can belong to multiple workspaces. Each workspace has its own membership and resource access; signing in does not grant access to every workspace.
Select or create a workspace
Use the workspace switcher in the dashboard to choose where you want to work. Create a separate workspace when a team or client needs independent membership, billing, or integration access.
Use projects and environments to organise related applications inside one workspace. Do not create extra workspaces merely to model staging and production for the same team.
Workspace settings
Open Workspace settings to manage the name, notification preferences, team members, build policy, registries, security settings, and activity exports available to your plan.
The workspace ID shown there is useful for API requests and support. It identifies the workspace but does not authenticate access.
Owners and admins can update workspace settings. Use team roles to grant narrower access to people who only need deployment or viewing capabilities.
Included access
| Capability | Without qualifying paid services | With a qualifying active paid service |
|---|---|---|
| Workspace members | 1 | Up to 10 |
| Environments per project | Up to 2 | Up to 20 |
| Shared build minutes | At least 500 per UTC month | Greater of 500 or pooled paid-service contributions |
| Private registry configuration | Not included | Included |
| Audit CSV export and workspace MFA enforcement | Not included | Included |
A paid service qualifies through its actual purchased, deployed access. A draft plan selection, suspended instance, or expired term is not equivalent to an active paid service. See Billing.
Personal two-factor authentication and baseline workspace access checks apply independently of these paid workspace benefits.
Notifications and build policy
Choose a verified workspace member's email for operational notifications and keep it monitored. Account and workspace notification preferences can control which deployment events produce messages.
Review overlapping-deployment behaviour and the shared pipeline allowance before enabling automatic deploys on many services. One concurrent build is included; editing customer preferences does not create extra infrastructure capacity. See Builds.
Activity and audit history
Workspace activity records changes such as service updates, member changes, and integration actions. Owners and admins with the audit-export entitlement can download a CSV for a selected date range of up to one year.
Use activity history to understand who changed a resource. It complements application logs, which describe the application's own runtime behaviour.
Leave or delete a workspace
Members can leave a workspace. The owner must transfer ownership before leaving. Deleting a workspace requires the owner, an explicit name confirmation, and removal of its service configurations first.
Do not use workspace deletion as a shortcut for suspending a paid application. Export required data, resolve billing records, and review every service before deleting resources.