About this block

Audit Log Preview shows the artifact compliance teams ask about. Five mono table rows render real looking entries, an export, an API write, an approval, a role change, and crucially the line the vendor own support session writes, granted by the customer, expiring in 24 hours. The copy names retention, seven years.

The entries are one array. The support session row is the trust master stroke, it demonstrates that even your access is logged in the customer view. Plausible emails and key fragments make the mockup read as a screenshot.

When to use

Reach for this block on trust pages and enterprise landings beside security-pillars-grid, the pillar says audit log, this shows it. Reviewers who see the actual log shape skip a demo question, and the mono table reads as product, not marketing.

A natural flow around it on a Marketing Pro page:

Before

• Security pillars naming the control this renders

After

• Security FAQ covering retention and export questions
• Enterprise CTA for the buyers this convinced

What you can display

One strong use is the workspace audit log with the support access line. Other logs:

• API access log. Key usage entries for a developer trust page.
• Data access log. Who viewed what for privacy sensitive products.
• Change history. Configuration changes for infrastructure buyers.

Tip: include your own support access as a logged line, no sentence about least privilege says it better.