1. Introduction Part of the Access Transparency manual — see also 2. What's New, 3. Scope, 4. Setup, 5. Usage, 6. Troubleshooting. 1.1 What Access Transparency does Access Transparency provides full visibility and traceability of user activity in GLPI. The plugin tracks and displays detailed user actions and object interactions across the system, with dedicated tabs on User and Document pages showing filterable, paginated activity logs and exportable CSV records. 1.2 Pain points it addresses GLPI's core logging is comprehensive but scattered: the Historical tab on an item shows what changed on that item, but there is no single view answering "what has this user done?" across the whole instance. This plugin closes that gap with a User-centric tab and Document-centric tab, reconstructing a user's activity from GLPI's own log tables, document-open events captured by the plugin's JS tracker, and system events. 1.3 Features Centralized user activity log showing actions performed by a user across all GLPI items Document view tracking recording file opens (via the plugin's JS tracker) Filterable and paginated views to locate specific actions by date, event type, field, or change Exportable activity logs from both full and filtered User/Document views as CSV Dedicated History tabs on User and Document pages, matching GLPI's native Historical tab styling Readable event-type labels (e.g. "User", "Profile", "Document") instead of raw internal names — a document open specifically shows as Event type "Document", Field "Current file", Update "File open" Automatic log retention with a configurable cron task to purge logs older than a set cutoff Excluded logins for service/system accounts (e.g. inventory, ocsinventory, glpi-agent) to prevent tracking noise No additional database fields required — the plugin leverages GLPI's existing glpi_logs and glpi_events tables plus a custom glpi_plugin_accesstransparency_userinteractions table for document opens Generated for Access Transparency 1.2.0-beta3 on GLPI 11.0.8 — 2026-08-24.