SeentySeenty Docs

Audit Logs

Track and review all actions taken within your Seenty organization with a chronological audit trail.

Audit Logs

Audit logs are an Enterprise-only feature. If you are on another plan and need audit capabilities, contact sales to discuss an Enterprise plan.

Audit logs provide a chronological record of every significant action taken within your organization. They answer the questions security and compliance teams care about most: who did what, when, and whether it succeeded.

What is tracked

Audit logs capture actions across all areas of the platform:

Team management

  • Member invited to the organization
  • Member removed from the organization
  • Member role changed (e.g., Editor promoted to Admin)
  • Ownership transferred to another member

API keys

  • API key created
  • API key revoked

Billing

  • Plan changed (upgrade or downgrade)
  • Payment method updated
  • Subscription cancelled

Assets

  • Domain added or removed
  • Cloud account (AWS) connected or disconnected
  • Repository connected or disconnected

Operations

  • Monitor created, updated, or deleted
  • Escalation policy created, updated, or deleted
  • On-call schedule created, updated, or deleted
  • Status page created, updated, or deleted

Organization settings

  • Organization name changed
  • Organization timezone changed

Event details

Each audit log entry includes:

FieldDescription
TimestampThe exact date and time (UTC) the action occurred
ActorThe user who performed the action (name and email)
ActionWhat was done (e.g., "member.role_changed", "monitor.created")
TargetThe resource affected (e.g., monitor name, member email)
ResultWhether the action succeeded or failed
DetailsAdditional context, such as the old and new values for a change

Filtering and searching

The audit log interface supports filtering by:

  • Date range -- View logs from a specific time period
  • Actor -- See all actions performed by a specific team member
  • Action type -- Filter to a specific category (e.g., only billing changes or only member management)

Retention

Audit log entries are retained for the duration of your Enterprise subscription. They are not subject to the standard data retention limits that apply to monitoring data.

Use cases

  • Incident investigation -- Understand what configuration changes were made leading up to an incident. For example, did someone modify a monitor's alert threshold or disable a notification channel?
  • Compliance -- Demonstrate to auditors that access controls are enforced and that all administrative actions are logged.
  • Onboarding review -- Verify that new team members were given the correct roles and permissions.
  • Security review -- Detect unusual activity, such as API keys being created or revoked outside of normal processes.