Skip to main content

4. Setup

logo

Part of the Access Transparency 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

The cron task PurgeInteractionLogs (class PluginAccesstransparencyUserinteractions, method PurgeInteractionLogs) runs on the schedule defined at registration time (default: hourly):

  • If retention is set to "keep all" (DELETE_ALL in PluginAccesstransparencyConfig), the task skips any deletion.
  • If retention is set to "delete all" (KEEP_ALL), every row in glpi_plugin_accesstransparency_userinteractions is deleted.
  • If retention is set to a number of months (e.g. "12 months"), rows older than current_time - (months * 30.44 * 24 * 3600) seconds are deleted.

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:

  1. Tab visibility — Session::haveRight('profile', READ) gates the Profile tab; Session::haveRight('plugin_accesstransparency_view', READ) gates the User and Document tabs. Both checks live in the respective class's displayTabContentForItem() method.
  2. CSV export — both export routes (front/export_user_csv.php and front/export_document_csv.php) check Session::haveRight('plugin_accesstransparency_view', READ) before serving the file.

Additionally, the CSV export routes respect standard GLPI visibility rules for the User or Document in question — a user can only export history for items they would otherwise be allowed to view.

Generated for Access Transparency 1.2.0-beta2 on GLPI 11.0.8 — 2026-08-24.

Back to top