Workspace 01
Customer platform
- Public API
- Customer portal
Members & roles set here
Alert destination
SlackPlatform responders
All solutions More teams.
Organizational example. Each workspace has its own configuration; this diagram does not represent a central policy-enforcement console.
Solutions / Enterprise
More teams.
One clear practice.
Give every service team a clear place to work. Bring monitoring, workspace access, and incident communication into a consistent operating practice as your organization grows.
Agree on
the essentials
the essentials
Coverage
Define the services that matter
Confirmation
Agree on evidence before escalation
Communication
Decide who needs the update
Workspace 02
Commerce systems
- Storefront
- Checkout service
Members & roles set here
Alert destination
EmailCommerce responders
Workspace 03
Identity services
- Authentication API
- Sign-in endpoint
Members & roles set here
Alert destination
WebhookIdentity responders
A shared approach, configured separately in each workspace.Services · Members · Destinations
01 / Workspace access
The right participation.
For each person.
Give people the access their work calls for. Explore selected permissions for the four built-in roles, assigned within each workspace.
Read the team access guideSelected workspace role
Owner
Oversee the workspace.
Manage workspace membership and the monitors, incidents and status pages your team maintains.
Access stays within the workspace.
02 / Incident practice
Different service owners.
A common starting point.
When a service fails, put regional observations, confirmation rules, and incident history in front of the team. Carry that context through the response and into the next handoff.
Inspect an example incident Checks establish the evidence.
Your team owns the response.
HTTP monitor
Public API
Confirm with evidence
Virginia and Frankfurt met the configured failure threshold.
2 consecutive failures · 2 of 3 regionsRoute the confirmed event
The platform team's Slack destination received the incident.
Delivery recordedKeep the recovery context
Successive healthy checks met the recovery threshold in the affected regions.
Observations and transitions retained
Keep both audiences
in the loop.
in the loop.
Inside the workspaceTechnical evidence, check history, and delivery outcomes.
On your status pageComponent health and updates you choose to publish.
03 / Enterprise evaluation
Make the fit clear.
Before the rollout.
Start with your operating requirements. Review security, check how alerts connect to your tools, and confirm the scope your teams need.
01 / EVALUATE
Review security.
Understand the documented security approach and bring the requirements your organization needs to evaluate.
- Security approach
- Organizational requirements
02 / EVALUATE
Connect your response.
Explore available destinations and the signed webhook workflow for the tools your responders already use.
- Email and Slack destinations
- Signed webhook workflow
03 / EVALUATE
Confirm the scope.
Match available features and plan limits to the services, workspaces, and people you need to support.
- Monitor and workspace limits
- Team and feature requirements
Bring your service inventory, team structure, and response requirements to the conversation.
Talk to our teamStart with your operating needs
Map the services.
Build a shared practice.
Let's talk about coverage, access, and your incident workflow.