Skip to main content

6. Troubleshooting

I don't see the Access Transparency tab

Check these in order:

  1. Your profile has the right. On Administration > Profiles > (your profile) > Access Transparency, Historical > Read must be ticked. The Super-Admin profile has it after installation; any other profile needs it ticked.
  2. The plugin is activated. On Setup > Plugins, Access Transparency must show as enabled.
  3. You can see the item. On a document, you also need to be allowed to see the document itself; on a user, the user.

The tab is empty, or recent actions are missing

Actions taken in GLPI reach the tabs when the Get logs automatic action runs, once an hour, so a very recent action can take up to an hour to show. If it never shows, check on Setup > Automatic actions that Get logs is scheduled and that GLPI's cron job is running: both actions use the CLI run mode. Document accesses do not wait for the automatic action, they are recorded as soon as the document is opened.

Some records seem to be missing

You only see what you could already see in GLPI. A record is left out when it refers to an item outside your entities, when you lack GLPI's Logs right (item changes) or System logs right (events), or, on a document, when the person who opened it is outside the users you can see. Ask a GLPI administrator to check your profile.

Nothing is recorded for a service account

That is expected if its login is in Excluded logins on Setup > General > Access Transparency. Nothing is recorded for those accounts, neither their changes nor their document accesses. Logins are compared without regard to capital letters; separate several of them with commas.

The export says the page was not found

The export is limited in the same way as the tab: you need the Historical > Read right and you must be able to see that user or document. Otherwise the export is refused, and a link opened after the plugin was deactivated also fails. If you cannot see the tab, you cannot export.

The export file is empty or has only the header row

The filters you set on the tab are applied to the export. Click Filter, clear the fields, and export again. If the unfiltered export is empty too, there are no records for that user or document: they may be older than the Log retention, or not yet copied by Get logs.

The export stops at 10,000 rows

An export holds at most the 10,000 most recent records, and the last row of the file says so. Use the filters (for example a date) to export the rest in parts.

Old records are not being deleted

The Purge old logs automatic action deletes records older than the Log retention setting, once an hour. Check that the retention is a number of months and not Keep all logs, that the action is scheduled on Setup > Automatic actions, and that GLPI's cron job is running.

Old records have disappeared

That is the same action at work: records older than the Log retention are deleted once an hour. Choose Keep all logs to keep them. The records of a user are also deleted when that user is purged from GLPI.

The settings do not save

Only a profile with the right to update GLPI's Setup > General can save them. GLPI also asks for your password before showing and before saving the settings; if you cancel that prompt, nothing is saved.

GLPI asks me for my password

GLPI 12 asks administrators to confirm their password before some actions: opening or saving the Access Transparency settings, or exporting the records of a user. This comes from GLPI itself.

A document opened through the API is not listed

Downloads made from GLPI's pages and through the High-Level API are recorded. The raw download of the legacy REST API is not.

Generated for Access Transparency 2.0.0 on GLPI 12.0.2 — 2026-11-20.