What's tracked

Two different records

It's worth being precise about what Snowmass keeps where. Your operational history and the audit log are two separate records, and they cover different things.

What the audit log records

The append-only audit log is deliberately narrow. It records exactly two kinds of privileged-access event, each stamped with the true user behind the action and the IP address it came from:

• Staff impersonation — when Snowmass staff start or stop acting inside your workspace on someone's behalf.
• Platform access — when platform-level access to your workspace is granted or revoked.

That's the whole scope. The audit log is not a feed of field or fleet activity — it's the record of who was let into the workspace, and who acted as whom.

What lives in reports instead

Your actual storm and field history isn't in the audit log — it's in reports, which you filter and export (see Running reports & exports). That's where you'll find:

• Events and passes — the status and timing of each storm and each sweep.
• Operators — runs per operator, distance covered, and recalls.
• Materials — what was applied, logged on arrival at a stop.
• Incidents — reports raised in the field, with any attached photos.
• Properties, contacts, and support cases — the record for each.
• Crew availability and confirmations — who was asked and who answered.
• A season summary — coverage and totals across storms.

Using them together

To reconstruct what happened at a property, filter a report to the date and property. To see who was granted access to your workspace, or who acted on a customer's behalf, consult the audit log. One is your operational history; the other is your privileged-access trail.