> For the complete documentation index, see [llms.txt](https://help.auxalia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.auxalia.com/plant-tools/planttools/change-log/workflows/change-log-in-collaboration-and-vault-projects.md).

# Change log in Collaboration and Vault projects

{% hint style="danger" %}
**Not released yet.** This page describes a function of an upcoming release.
{% endhint %}

In a Collaboration project on Autodesk Docs and in a Vault project, the change log files are project files like the drawings and are shared with the project. Recording and reading work as in the other workflows, with these differences:

1. The history is shared: the changes of your colleagues appear in your history, and yours in theirs.
2. The first save of a drawing that records something downloads that drawing's change log file and checks it out - **Writing Change Log Data** shows the progress. The file stays checked out while the drawing is open, so the later saves do not need the server.
3. Closing the drawing checks the file in again - or undoes the check-out if nothing was recorded.
4. A change of a drawing or of the project takes the project's change log file from the server for a moment and checks it in right after. The **Change Log** tab of PlantProjectManager downloads it to show the latest entries.
5. The Properties Palette and PlantDataManager show the change log files as they are on this computer. They can be behind the server until a file is downloaded again - for a drawing, by its next save that records something.
6. In a project on SQL Server the change log is one central database: nothing is downloaded or checked out.

The **Change Log** tab and PlantDataManager's views show the changes of all users, each with its own **User**.
