4. Setup


Part of the Access Transparencyaccesstransparency manual — see also 1. Introduction, 2. What's New, 3. Scope, 5. Usage, 6. Troubleshooting.
4.1 Installation
4.2 Configuration
4.2.1 Automatic actions
ThePurge cronold taskinteraction PurgeInteractionLogslogs (classSetup PluginAccesstransparencyUserinteractions,→ methodAutomatic PurgeInteractionLogs)actions) runsautomatically deletes old document-open records once they're older than the retention period configured on the schedule"Access definedTransparency" atconfiguration registration timepage (default:Setup hourly)→ General → "Access Transparency" → "Log retention"):
IfKeepretentionall — nothing issetevertodeleted.
DELETE_ALL— PluginAccesstransparencyConfigKEEP_ALLglpi_plugin_accesstransparency_userinteractions"12only months"current_timethat - (months * 30.44 * 24 * 3600)The task is called via Session::addMessageAfterRedirect() logging the number of deleted rows.
4.3 Permissions
The plugin enforces one right, checked at two points:
displayTabContentForItem()front/export_user_csv.phpfront/export_document_csv.phpSession::haveRight('plugin_accesstransparency_view', READ)Additionally, the CSV export routes respect standard GLPI visibility rules for thea User or Document page requires the Historical permission on the logged-in questionuser's profile (Administration → Profiles → profile → "Access Transparency" tab). It's Read-only — athere's usernothing to grant beyond "can see it or can't." CSV export uses the same permission: if you can onlysee the tab, you can export historyit, and only for itemsUsers/Documents they wouldyou're otherwise be allowed to view.
Generated for
Access Transparencyaccesstransparency 1.2.0-beta2 on GLPI 11.0.80 — 2026-08-24.