๐ Teams Overview
Monitron SaaS supports multi-team organization. Each team has its own monitors, incidents, contacts, and status pages โ completely isolated from other teams.
๐๏ธ How Teams Workโ
Organization
โโโ Team: Production
โ โโโ Monitors (web servers, APIs, databases)
โ โโโ Incidents
โ โโโ Contacts (on-call team)
โ โโโ Status Page: status.example.com
โ
โโโ Team: Staging
โ โโโ Monitors (staging servers)
โ โโโ Incidents
โ โโโ Contacts (dev team)
โ
โโโ Team: Client Projects
โโโ Monitors (client websites)
โโโ Status Page: status.client.com
๐ Team Isolationโ
Each team's data is completely scoped:
| Resource | Scoped to Team |
|---|---|
| Monitors | โ |
| Monitor Checks | โ (via monitor) |
| Incidents | โ |
| Contacts & Groups | โ |
| Alert Rules | โ |
| Status Pages | โ |
| Server Agents | โ |
| Notification Logs | โ |
System-wide settings (email config, AI config, notification provider keys) are shared across all teams.
๐ค User Rolesโ
| Role | Permissions |
|---|---|
| Owner | Full access, can delete the team |
| Admin | Manage monitors, contacts, settings |
| Member | View monitors, acknowledge incidents |
๐ง Creating a Teamโ
A default team is created during installation. To create additional teams:
- The admin can create teams from the dashboard
- Each team gets a unique slug
- Users can be invited to teams
๐ Switching Teamsโ
Users who belong to multiple teams can switch between them. The currently selected team determines which monitors, incidents, and other resources they see.