Workspaces
Workspaces are the foundation of a11ops, providing isolated environments for organizing your alerts, team members, and integrations. Each workspace operates independently with its own configuration and access controls.
What are Workspaces?
A workspace is a completely isolated environment within a11ops that contains:
- All alerts sent to that workspace
- Team members with specific roles and permissions
- API keys for programmatic access
- Integration configurations
- Alert routing rules and preferences
Complete Isolation
Each workspace is completely isolated. Alerts, data, and configurations never cross workspace boundaries.
Team Collaboration
Invite team members to specific workspaces with role-based access control for secure collaboration.
Creating a Workspace
- Log in to your a11ops account
Navigate to dashboard.a11ops.com and sign in
- Click “Create Workspace”
Found in the workspace selector or settings
- Choose a descriptive name
E.g., “Production”, “Staging”, “Team Alpha”
- Configure initial settings
Set up team members and generate your first API key
API Keys
Each workspace has its own unique API keys for sending alerts programmatically. API keys are:
- Unique 32-character hexadecimal strings
- Scoped to a single workspace
- Used in the alert endpoint URL path
- Revocable and regeneratable at any time
API Key Best Practices
- •
Never commit API keys to version control
Use environment variables or secure key management
- •
Use different keys for different environments
Separate keys for development, staging, and production
- •
Rotate keys regularly
Implement a key rotation policy for enhanced security
- •
Monitor key usage
Track which services are using which keys
Team Management
Adding Team Members
Invite team members to collaborate in your workspace:
- Navigate to workspace settings
- Click on “Team Members”
- Enter the email address of the person to invite
- Select their role (Admin, Member, or Viewer)
- Send the invitation
Roles and Permissions
Admin
Full access to workspace settings, can manage team members, API keys, and integrations
Member
Can view alerts, acknowledge them, and access workspace data but cannot modify settings
Viewer
Read-only access to alerts and workspace data, cannot make any modifications
Workspace Configuration
Alert Preferences
Configure default alert behaviors, retention policies, and auto-acknowledgment rules
Integrations
Set up webhooks, connect monitoring tools, and configure alert routing
Security Settings
Manage API keys, configure IP allowlists, and set up SSO authentication
Team Policies
Define on-call schedules, escalation policies, and notification preferences
Common Use Cases
Environment Separation
Create separate workspaces for different environments:
Production
Critical alerts only
Staging
Pre-production testing
Development
All alert levels
Team-Based Organization
Organize workspaces by team or service ownership:
- Frontend Team - UI/UX related alerts
- Backend Team - API and database alerts
- DevOps Team - Infrastructure and deployment alerts
- Security Team - Security events and compliance alerts
Customer Isolation
For multi-tenant applications, create separate workspaces per customer to ensure complete data isolation and provide customer-specific alert management capabilities.
Limits and Quotas
Workspace limits are based on your subscription plan:
| Feature | Free | Starter | Team | Enterprise |
|---|---|---|---|---|
| Workspaces | 1 | 3 | Unlimited | Unlimited |
| Team Members | 1 | 5 | Unlimited | Unlimited |
| API Keys | 2 | 10 | Unlimited | Unlimited |
| Alert Retention | 1 day | 7 days | 30 days | Custom |
Next Steps
Learn more about alerts and how to structure them effectively.