📖 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:
| Ressource | Portee Equipe |
|---|---|
| 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.