Organize service context
Keep monitors, incident records, team members and integrations together in the appropriate workspace.
All solutions More teams.
Undown for enterprise teams
More teams.
Clearer lines
of responsibility.
Give service teams a consistent way to monitor availability, investigate incidents and communicate updates. Keep workspace access and operational context explicit as your organization grows.
A shared operating practiceIllustrative structure
Agree on the essentials
Coverage. Confirmation. Communication.
Define the monitoring and response approach your service teams will follow.
Customer platform
Public API + customer portal
Workspace members · Monitors · Alert destinations
Commerce systems
Storefront + checkout service
Workspace members · Monitors · Alert destinations
Identity services
Authentication endpoints
Workspace members · Monitors · Alert destinations
Organizational example. Each workspace is configured separately; this is not a central policy-enforcement console.
Consistency without losing context
A common practice.
A workspace for the work.
Start with the services each team operates. Give members access to the workspace they need, configure its monitors and destinations, and agree on how incidents will be communicated.
Make access deliberate
Assign built-in roles so people can administer, contribute to, or observe the workspace.
Decide where updates belong
Configure alert destinations for responders and publish customer-facing updates on status pages.
Workspace access, made explicit
The right participation
for each person.
Explore a selection of permissions for the four built-in workspace roles. Membership and access are assigned within each workspace.
Owner
Oversee the workspace.
Manage workspace membership and the monitors, incidents and status pages your team maintains.
Repeatable incident response
Different service owners.
The same need for evidence.
Bring regional observations, confirmation rules and incident history into the response. Give each team a useful starting point when a service fails.
Inspect an example incidentDefine confirmation per monitor
Choose consecutive-failure and regional confirmation thresholds appropriate to the monitored service.
Route confirmed events
Connect email, Slack or signed webhook destinations and review delivery outcomes when notifications need attention.
Retain the incident context
Review the observations and transitions that supported confirmation and recovery, alongside published updates.
Evaluate against your requirements
Make the fit clear
before you roll it out.
Review security
Review the documented security approach and discuss the requirements your organization needs to evaluate.
Read about securityCheck integration fit
Explore available destinations and the signed webhook workflow for connecting your existing tools.
Explore integrationsConfirm scope and limits
Review plan limits and available features against your monitor, workspace and team requirements.
Review pricingStart with your operating needs
Let's map the services,
the teams, and the response.
Tell us about your monitoring coverage, access requirements and incident workflow.