B2B Audit Trail
The B2B Audit Trail is a cross-Company-scoped view of every action taken on cross-Company requests, connections, and registry entries. It's the same event log as the internal Audit Trail but filtered to entities that involve at least one partner Company.
Open from B2B → Audit Trail.
Why a separate B2B view
Internal audit + B2B audit are two slices of the same underlying log. Splitting the views serves three goals:
- Compliance reporting — auditors evaluating your B2B SLA / data-handling commitments often need a partner-scoped log without internal noise
- Partner disclosure — a partner can request a copy of B2B-scoped audit entries that involve them; it's much faster to scope this view than to filter the full log
- Operational triage — the team handling cross-Company work doesn't need internal IAM events in their feed
What's logged
Every B2B-relevant action emits an audit row, including:
| Action | Triggered when |
|---|---|
b2b.connection.requested | Either Company submits a connection request |
b2b.connection.accepted / .rejected | Receiving Company decides on a request |
b2b.connection.revoked | Either Company terminates an active connection |
b2b.request.submitted | Cross-Company request created |
b2b.request.accepted / .rejected / .cancelled | Triage decisions on the receiving side |
b2b.request.status.changed | Provider Company pushes a status update visible to the consumer |
b2b.request.message.sent | External-facing message added to the conversation thread |
b2b.sla.target.met / .missed | When an SLA timer resolves on a completed request |
b2b.registry.published / .updated / .unpublished | Public-audience service lifecycle events |
Per-row fields
- Timestamp (your timezone)
- Action (the event type from the table above)
- Actor — the User, Agent, or service principal that took the action
- Actor Company — your Company or the partner
- Target — the request, connection, or service the action operated on
- Partner Company — the other side of the cross-Company link
- Details — JSON blob with action-specific metadata (e.g. status transition
from/to, message content snippet, SLA target / actual)
Filtering
- Action — multi-select on the action types above
- Actor Company — your Company / specific partner / all
- Date range
- Search — text-matches actor name, target ID, message content
- Partner Company — narrow to one specific partner
Exporting
The page has an Export button that generates a JSON or CSV file respecting the current filter state. Use this to satisfy partner audit requests or feed external SIEM tools.
For programmatic access (real-time SIEM integration), use the API Reference — /audit/events accepts the same filters and supports pagination.
Retention
B2B audit events follow your Company's broader audit retention policy (configurable in Company Settings; default is 365 days in hot storage, then archived for compliance retention up to 7 years on plans that include extended retention).
Both Companies retain their own copy. Neither side can delete the other's record.
Related
- Audit Trail (internal) — the broader event log
- B2B Requests — request list this audit rolls up from
- Connections — partner relationship state