Team Collaboration for Synthetic Monitoring

Monitoring is a team sport. supaguard offers unlimited seats on all plans — including the free tier — so your entire engineering team can access dashboards, investigate failures, and manage checks without per-seat costs.

Inviting Team Members

Adding Members to Your Organization

1. Go to Settings → Team
2. Click Invite Member
3. Enter their email address
4. Select their role
5. Click Send Invite

The invited member receives an email with a link to join your organization.

Role-Based Access

[!TIP] Use the Member role for most engineers. Reserve Admin for team leads who manage alert policies and integrations. Viewer is useful for stakeholders who want visibility without configuration access.

Organizing Checks

As your monitoring coverage grows, organization becomes essential:

Naming Conventions

Use consistent naming to make checks searchable and sortable:

[Environment] [Flow] — [Detail]

Examples:

• [Prod] Login — Credentials
• [Prod] Checkout — Stripe Payment
• [Staging] Dashboard — Data Loading
• [Prod] API — Products Endpoint

Grouping by Criticality

Organize checks into logical groups based on business impact:

Shared Alert Policies

Create alert policies that the whole team can use:

1. Critical — Page On-Call: PagerDuty + Slack #critical. For revenue and auth flows
2. Warning — Slack: Slack #monitoring. For important but non-urgent issues
3. Informational — Email: Daily digest email. For low-priority checks

[!NOTE] Alert policies are organization-wide. Any team member with Member role or above can assign policies to their checks. This ensures consistent alerting behavior across the team.

Team Workflow Patterns

On-Call Rotation

1. Set up a PagerDuty integration with your team's on-call schedule
2. Assign "Critical" alert policies to revenue-critical checks
3. On-call engineer receives alerts and investigates using the debugging tools
4. Fix the issue or acknowledge the alert if it's a known problem

Post-Incident Review

When a synthetic check catches a real outage:

1. Review the failure timeline — video, traces, and network data
2. Identify the root cause using the debugging dashboard
3. Document the incident and resolution
4. Update monitoring if needed (new checks, adjusted assertions)

During Deployments

Coordinate monitoring during deployments:

1. Before deploy: Verify all checks are green
2. During deploy: Optionally mute alerts for 5-10 minutes (via check settings)
3. After deploy: Trigger CI/CD checks to verify the release
4. Monitor: Watch the dashboard for 15-30 minutes after deploy

Unlimited Seats Advantage

Unlike competitors that charge per seat, supaguard includes unlimited team members on every plan:

This means you can invite:

• The entire engineering team
• DevOps and SRE teams
• Product managers and stakeholders
• QA engineers
• Customer support (with Viewer role)

→ Pricing Plans for full plan details

Best Practices

1. Invite everyone — The more eyes on monitoring, the faster issues get resolved
2. Use roles appropriately — Don't give everyone Admin. Member is sufficient for most engineers
3. Standardize naming — Consistent check names make the dashboard scannable
4. Share alert policies — Don't create per-person policies. Use team-wide standards
5. Review together — Include monitoring results in sprint retros or weekly standups

Next Steps

• Quick Start Guide — Set up your first check
• Configuring Alerts — Alert policy design
• Billing & Pricing — Plan details
• How-To Guides — Common tasks step by step