Workspace Management
Organize resources, environments, credentials, billing, and team access with separate workspaces.
Best for
Workspace owners, admins, security reviewers, and finance stakeholders
Workspaces are the top-level container in PromptRails. Every resource -- agents, prompts, data sources, tools, credentials, executions, traces, API keys, billing records, and team members -- belongs to one workspace.
Use separate workspaces when you need isolated environments, teams, credentials, or billing. A staging workspace and a production workspace cannot accidentally share credentials or traces.
When To Split Workspaces
Use one workspace when a team shares the same agents, credentials, traces, and billing owner. Split into separate workspaces when isolation matters:
- Environment isolation -- Keep staging traces, credentials, API keys, and test agents away from production.
- Team isolation -- Give separate teams their own resources and member lists.
- Billing isolation -- Track usage, invoices, and hosted-model balance separately.
- Security isolation -- Prevent credentials or data sources from being reused across unrelated products.
Admin Surfaces
Most workspace administration lives under Settings. The important areas are:
| Area | Use it for |
|---|---|
| Members | Invite teammates, review access, and remove users who no longer need entry |
| Credentials | Store provider keys, database connections, and tool secrets |
| API Keys | Create scoped keys for SDKs, CLI, triggers, and external services |
| Notifications | Route workspace events to Slack or webhook destinations |
| Data Masking | Control outbound PII masking and masking overrides |
| Changelog | Review workspace-level created, updated, and deleted resources |
| Billing | Manage plan, invoices, hosted-model balance, and usage |
Creating Workspaces
Create a workspace through the PromptRails dashboard:
- Open the workspace switcher.
- Select Create Workspace.
- Enter the workspace name and slug.
- Confirm creation.
When a user creates a workspace, they automatically become the owner of that workspace.
Workspace Changelog
Settings > Changelog is the workspace audit trail. Use it when you need to understand what changed in a workspace, who or what made the change, and which resource was affected.
Use this view during reviews, incident follow-up, or handoffs between admins. It is different from the public product changelog, which summarizes PromptRails releases.
Technical detailsWorkspace settings and limits
Workspace Slug
Each workspace has a unique slug:
- Must be lowercase alphanumeric with hyphens
- Must be unique across the platform
Example slug:
my-company-stagingWorkspace Settings
Update workspace settings from Settings. The workspace name appears in navigation, invitations, and billing records. The slug is stable for links and cannot be changed after creation.
Workspace Scope
All resources in PromptRails are workspace-scoped:
| Resource | Workspace-Scoped |
|---|---|
| Agents | Yes |
| Prompts | Yes |
| Credentials | Yes |
| Data Sources | Yes |
| MCP Tools | Yes |
| Executions | Yes |
| Traces | Yes |
| Chat Sessions | Yes |
| Memories | Yes |
| Scores | Yes |
| Guardrails | Yes (via agent) |
| API Keys | Yes |
| Agent Triggers | Yes |
| Approvals | Yes |
| Apps | Yes |
This means resources in one workspace are completely isolated from another workspace. A credential in workspace A cannot be used by an agent in workspace B.
Plans and Limits
Each workspace is associated with a billing plan that defines resource limits:
- Maximum number of monthly executions
- Maximum number of active agents
- Maximum number of team members
- Maximum number of data sources
- Feature flags (memory, approvals, MCP, etc.)
See Billing and Plans for details.
Related Topics
- Team and Roles -- Managing workspace members
- Notifications -- Routing workspace events to Slack or webhooks
- Changelog -- Product releases and the in-app workspace activity log
- Billing and Plans -- Workspace billing configuration
- API Keys and Scopes -- Workspace-scoped API keys