Workspaces help you organize your Redis connections and keep different environments separate. Each workspace contains its own connections, alerts, and settings.
What is a Workspace?
A workspace is a container within an organization that groups related Redis connections together. Common use cases:
- By environment: Development, Staging, Production
- By project: Project A, Project B
- By team: Backend Team, Data Pipeline Team
Creating a Workspace
Navigate to your organization
Select your organization from the sidebar.
Click Create Workspace
Click the Create Workspace button.
Enter workspace details
| Field | Description | Example |
|---|
| Name | Display name for the workspace | Production |
| Slug | URL-friendly identifier (auto-generated) | production |
Save
Click Create to create the workspace.
Slugs can only contain lowercase letters, numbers, and hyphens. They must be unique within your organization.
Workspace Limits
The number of workspaces you can create depends on your subscription plan:
| Plan | Workspaces |
|---|
| Free | 1 |
| Pro | 5 |
| Enterprise | 10 |
Need more workspaces? Contact us about Enterprise options. Workspace Contents
Each workspace contains:
Redis Connections
Connect to one or more Redis instances within a workspace. See Connection Overview for setup instructions.
| Plan | Connections per Workspace |
|---|
| Free | 1 |
| Pro | 5 |
| Enterprise | 10 |
Alerts
Configure alerts for queues within the workspace. Alerts are scoped to a specific connection and queue.
Alerts require a Pro or Enterprise plan.
Workspace Settings
Rename Workspace
- Go to the workspace
- Click Settings in the sidebar
- Update the Name field
- Click Save
Change Slug
- Go to workspace Settings
- Update the Slug field
- Click Save
Changing the slug will change all URLs for the workspace. Update any bookmarks or shared links.
Delete Workspace
- Go to workspace Settings
- Click Delete Workspace
- Type the workspace name to confirm
- Click Delete
Deleting a workspace permanently removes all connections and alerts. This action cannot be undone.
Workspace Members
Workspace access is inherited from organization membership. All organization members can access all workspaces within that organization.
Member Roles
| Role | Permissions |
|---|
| Owner | Full access: manage connections, alerts, settings, delete workspace |
| Member | View and interact: view queues and jobs, retry/remove jobs (if read-write) |
Best Practices
Environment Separation
Create separate workspaces for each environment:
Organization: My Company
├── Workspace: Development
│ └── Connection: localhost Redis
├── Workspace: Staging
│ └── Connection: staging.redis.example.com
└── Workspace: Production
└── Connection: prod.redis.example.com
Keep production and development separate to prevent accidental operations on production queues.
Consistent Naming
Use clear, consistent naming conventions:
| Good | Avoid |
|---|
production | prod |
staging | stg |
development | dev-1 |
project-api | api |
Use Read-Only for Production
When setting up production connections, consider using Read-Only access mode to prevent accidental job modifications.
Switching Workspaces
To switch between workspaces:
- Click the workspace name in the sidebar
- Select a different workspace from the dropdown
- Or use the organization dashboard to see all workspaces
Next Steps
