Skip to main content
On this page

Audit trail & change attribution

In property management, auditability is a regulatory and operational necessity. When automated workflows and autonomous AI agents read and modify tenant data, “something changed” is insufficient. The etg24 platform records every state change with comprehensive, tamper-evident attribution.

The three fundamental questions

Every action recorded in the platform’s audit trail answers three questions conclusively:

  1. What changed? The exact entity type, entity ID, and a field-level diff comparing previous and new values.
  2. Who changed it? The specific actor identity — an automated bot, an external partner integration, or a human user.
  3. When did it happen? An immutable, millisecond-precision UTC timestamp.

There is no anonymous “the API updated a record”. Every modification is tied to an explicit API credential and actor identity.

Anatomy of an audit log entry

The audit trail is structured to provide machine-readable event streaming and inspection. A representative change log entry looks like this:

{
  "id": "evt_01J8K3M9NP7Q4VR5WXYZ123456",
  "timestamp": "2026-03-24T14:32:00.123Z",
  "actor": {
    "type": "agent",
    "name": "invoice-processing-bot",
    "keyId": "key_01J8K1AB90CDEF1234567890",
    "binding": "tenant",
    "delegatedUser": null
  },
  "entity": {
    "type": "Contract",
    "id": "ctr_98765432-1234-abcd-ef01-23456789abcd",
    "propertyId": "obj_12345678-abcd-1234-5678-abcdef123456"
  },
  "action": "update",
  "changes": [
    {
      "field": "billingCycle",
      "oldValue": "monthly",
      "newValue": "quarterly"
    }
  ],
  "context": {
    "ipAddress": "198.51.100.42",
    "requestId": "req_88f912e4b01c"
  }
}

Discrete per-agent attribution

Multi-agent environments require discrete accountability. In modern property management, an organization might deploy several distinct automated workflows:

  • A nightly ERP synchronization script
  • An AI inbox triage bot categorizing maintenance issues
  • An automated document extraction pipeline
  • An interactive assistant configured by an individual property manager

Rather than sharing a generic API key across all these systems, etg24 enforces one key per agent. Each key carries a human-readable agent name and unique identifier that remains continuous throughout its lifecycle.

Isolating rogue behavior

If an automated process malfunctions or encounters an unhandled edge case, granular attribution allows you to pinpoint the exact actor responsible. You can immediately disable that single agent key in the portal settings without interrupting other integrations or human staff.

Delegation: User-bound vs. Tenant-bound

Attribution explicitly distinguishes between two operational modes:

  • User-bound agents act on behalf of a specific staff member (e.g. an AI drafting emails for a manager). Log entries attribute actions to that employee’s assistant.
  • Tenant-bound agents act on behalf of the company as an entity (e.g. nightly migrations, background webhooks, ERP synchronizers).

Learn more about configuring these modes in Identity & delegation.

Foundation of safety and recovery

Audit attribution works in tandem with our recovery architecture:

  • Permission scopes define what an agent is allowed to do.
  • The audit trail records exactly what it executed.
  • Soft delete & rollback ensures that accidental or erroneous changes can be cleanly reversed.