The documentation logs in Tuleap allow you to track all actions performed on documents and folders in the document manager. They provide complete traceability of activities: who did what, when, and on which item. This feature is essential for collaboration, auditing, and monitoring the evolution of a project’s documentation.
What are “documentation logs”?
Logs (or history) correspond to the event journal recorded by Tuleap for each document or folder. They are not limited to file content: they cover all management actions.
Logs allow you to:
Understand the evolution of a document.
Identify the author of a modification.
Verify compliance with processes (reviews, approvals, updates).
Meet auditing or compliance requirements.
Where to view the logs of a document or folder
On the desired document or folder, open the action menu and select “Logs”.
The history screen then displays the list of events associated with the document or folder.
Actions recorded in the logs
Documentation logs include the following events:
Document Management
Creation of a document.
Addition of a new version of a document.
Deletion of a document.
Download or viewing (depending on configuration).
Folder Management
Creation of a folder or subfolder.
Moving a document from one folder to another, or moving a folder itself.
Deletion of a folder (and its contents).
Properties and Metadata
Modification of the title or description.
Changes to custom properties.
Update of the document status (if used).
Security and Access
Change to permissions (reader, author, manager).
Modification of access rules on a document or folder.
Information Visible in a Log
Each log entry shows:
The date and time of the action.
The user who performed the action.
The type of action performed.
The previous and new value.
This information provides a clear and usable audit trail.
Difference between logs and versions
It is important to distinguish:
Activity logs
Provide overall traceability of actions.
Include content changes as well as management actions (permissions, moves, deletions).
Document versions
Track the content history of a document.
Each version represents the state of the file at a specific point in time.
Logs provide context, versions provide content. Logs are the form, versions are the substance.
Access rights to logs
Log visibility depends on permissions:
Reader: can view the document and its history.
Author: can view logs and create new versions.
Manager: full access, including permission changes.
If the “Logs” option is not visible, it usually means the user’s rights are insufficient.
Logs and notifications
Logs can be complemented with notifications:
By subscribing to a document or folder, you receive an email when an action is recorded (new version, modification, move, etc.).
Notifications keep you informed without manually checking the logs.
Logs are for post-event analysis, while notifications provide real-time information.
Best practices for using logs
Check the history before modifying an important document.
Use logs to identify the origin of an error or deletion.
In a team, rely on logs to clarify responsibilities.
For critical projects, integrate log review into quality audits.