# Contents

Daytona now provides Audit Logs, a complete record of user and system activity across your organization. With Audit Logs you can track sandbox lifecycle events, user actions, and system changes in one place, giving you the visibility and control needed for security, debugging, and compliance.

Why Audit Logs

As teams scale, knowing what happened, when, and by whom becomes critical. Audit Logs give administrators and members the ability to:

  • Monitor security: Detect unauthorized access or sandbox misuse

  • Debug issues: Trace sandbox lifecycle errors such as failed starts

  • Meet compliance needs: Export logs for audits and reporting (export support coming soon)


Accessing Audit Logs

You can view Audit Logs directly from the Dashboard.

  • Admins: Full access to all logs across the organization

  • Members: Access only if granted the correct permissions

If you do not see the logs, contact your organization admin for access.


Real-Time Updates

Enable the Real-Time Updates toggle on the Audit Logs page to automatically refresh the log view as new events occur.

Log Structure

Each log entry includes:

FieldDescription
UserTimestamp (UTC) of the action
ActionEmail of the user who performed the action
TargetResource type affected
OutcomeResult status code and message
1Time: 5h ago (7/31/2025, 8:15:27 AM)
2User: janedoe@acme.com
3Action: create
4Target: sandbox (ID: 10f249ad-...)
5Outcome: Success (200)

Actions Logged

Daytona captures a wide range of actions including:

  • Lifecycle operations: create, update, delete, start, stop, archive

  • User management: login, update_role, accept/decline invitations

  • Access and security: regenerate_key_pair, link_account, suspend

  • Toolbox activity: file operations, git commands, command execution

  • System changes: update_network_settings, scheduling, backups

For the full list of supported actions, visit the documentation.

Targets and Outcomes

  • Targets: Actions are tied to specific resources such as sandboxes, snapshots, users, volumes, and organizations.

  • Outcomes: Results follow standard HTTP semantics (Success 2xx, Error 4xx/5xx, etc.).

Example outcomes:

  • 200 Success – Sandbox created

  • 400 Error – Sandbox is not started

  • 403 Error – Unauthorized

  • 500 Error – Internal system error

Try It Now

Audit Logs are available today for all organizations on Daytona.

Head over to your Dashboard to start monitoring activity in real time:
👉 Log in to Daytona

Tags::
  • Daytona
  • Audit Logs
  • sandbox security
  • compliance
  • monitoring
  • logging
  • system activity
  • developer tools
  • real-time logs
  • cloud development