Sign in

Record cross-tenant actions in the company's audit trail

Whenever a host-side user — the Platform Operator or the host administrator — acts on a company, the platform records the action in that company's own audit trail, so the company's Owner and Admins can see everything the vendor did.

When this happens: A host action targeting a company completes.

Step by step

  1. 1

    Performs a host action on a company (e.g. Restores Owner access — UC-1.15).

    Within the same unit of work, writes an audit entry with the company as tenant: action, timestamp, host actor id and name. And the reason where one is required. Commits the action and the entry together.

  2. 2

    Later opens the audit log and sees the entry with a Platform badge.

  3. 3

    Filters the log on host actions to review everything the vendor did.

Other paths

Inspection session

If for an inspection, writes one entry per inspection session listing the sections viewed, not one per request.

If something goes wrong

Audit entry cannot be written

At step 2 the company-side entry cannot be written. The whole action is rolled back and the Platform Operator sees The action could not be recorded in the company's audit trail and was not applied

Good to know

  • A host action on a company without a matching entry in that company's audit trail must not exist.
  • Host-action entries are append-only; company Admins can read but not edit or delete them.
  • Entries never contain message content or customer data. (FR-01-040, ADR-013)