An audit log lets admins trace who did what, to which resource and when. Our examples show a filterable event table with actor, action, target, IP address and time, plus an event detail panel, designed for a fictional workspace product on web and mobile in eight visual styles with light and dark themes. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.
16 examples
Each event should record who acted, what they did, what it affected, when it happened and from where, such as an IP address or device. A detail view can show before and after values and any request metadata investigators need.
No. Audit logs should be append-only so they remain trustworthy as a record. Admins can filter, search and export entries, and older events may be archived under a stated retention policy, but individual entries should not be altered from the interface.
Use server-side filtering and pagination or infinite loading rather than loading everything at once. Encourage narrowing by date range and event type, and provide export for deeper analysis. Keep the table columns compact so many rows fit on screen.
App screens
UI components
Website sections
Website templates
search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.