Governance
Access control and auditability for enterprise monitoring.
SenalOps includes organization roles, team membership controls, invitation management, API key governance, audit logs, owner-only owner management, and last-owner protection. Configuration and response activity can be traced from the audit log.
Why observability needs governance
Monitoring configuration decides who gets paged, which alerts fire, and which API keys can write telemetry. When that configuration changes without a record, incidents get harder to explain and security reviews get harder to pass. SenalOps treats access and configuration as governed data: every important change has an owner, a permission check, and an audit entry.
Role based access control
- Owners have full organization control, including owner grants and critical access management
- Admins manage monitors, services, routing, alerting, API keys, and teams
- Members view operational data and take part in incident response
- Owners can add explicit allow or deny overrides for reports, integrations, routing, API keys, and incidents
An audit trail for every important change
The audit log captures the actor, action, target, timestamp, and metadata for monitor, alerting, API key, service, routing, incident, review, and access changes. Owners and admins can review it after configuration changes, use it during incident reviews, and export it as CSV or JSON as evidence for security reviews.
FAQ
Observability governance questions
What enterprise governance features are included?
SenalOps includes organization roles, team membership, fine-grained permission overrides, API key management, audit logs and exports, owner/admin/member permissions, last-owner protection, invitation management, alert routing controls, tenant export/deletion requests, and post-incident review records.
What roles does SenalOps support?
Organizations have owner, admin, and member roles. Owners have full control, admins manage operational configuration such as monitors, services, routing, alerting, API keys, and teams, and members view operational data and take part in incident response. Owners can also add explicit allow or deny overrides for product areas.
What does the SenalOps audit log record?
The audit log records monitor, alert channel, API key, service, team, SLO, routing, maintenance, on call, report, integration, incident, review, and access changes. Each entry includes the actor, action, target, timestamp, and metadata.
Who can view and export the audit log?
Audit log access is limited to organization owners and admins, and records are scoped to the current organization. Audit evidence can be exported as CSV or JSON when audit export is enabled by organization policy.
What is last owner protection?
Only owners can manage owner access, and SenalOps blocks removing or demoting the last owner of an organization. That way an organization always keeps an accountable owner.
How do team invitations work?
Invite people by email with a role from Team and access. Existing users are added directly, new users get a pending invitation that is accepted when they sign up or sign in, and pending invitations can be revoked at any time.