Workspaces & Projects

SiroPing organizes monitoring around workspaces (tenants) and projects (client groups) — built for agencies that monitor many clients from one server.

Workspace = a tenant

• A Workspace is one isolated tenant: one company, or one agency client.
• Data between workspaces is fully isolated — members of one workspace never see another's monitors, incidents, channels or reports.
• Edition limits: Community/Pro = 1 workspace, Business = 10 workspaces (one per client).

Project = a group inside a workspace

Inside a workspace, Projects group the monitors of one client/system:

Workspace: Client A
  └── Project: Main website
        ├── HTTP: example.com
        └── Heartbeat: Nightly backup
  └── Project: API
        ├── HTTP (POST): /api/v1/status
        └── SSL: api.client-a.com

• Create a project, then assign monitors to it.
• Deleting a project does not delete its monitors.
• Reports and status pages are per project.

Switch workspaces

Use the workspace switcher in the sidebar. A user can belong to several workspaces with a different role in each.

Typical agency (Business) workflow

1. One workspace per client (up to 10).
2. Add each client's sites/APIs as monitors inside that client's project.
3. Add the client contact as a Member so they see their own monitors and nothing else.
4. Monthly white-label report + public status page per client are the deliverables.

See Team & Roles for invitations and permissions.