> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/openbrim/getting-started/navigation-within-openbrimapp/projects/projects-revisions.md).

# Projects Revisions

OpenBrIM automatically saves project revisions to the cloud, creating a complete history of all changes made by any user.

***

## Viewing Revisions

Click **Revisions** in the left sidebar to view all saved revisions organized by date.

<figure><img src="https://openbrim.atlassian.net/wiki/download/attachments/2101411862/image-20230327-094527.png?api=v2" alt="Revisions list"><figcaption><p>Revision history by date</p></figcaption></figure>

***

## Revision Actions

| Action           | Description                                                                   |
| ---------------- | ----------------------------------------------------------------------------- |
| **Share**        | Copy a shareable link to a specific revision                                  |
| **View Changes** | See modification history including date, time, user, and step-by-step changes |
| **Revert**       | Restore the project to a previous revision                                    |
| **Copy Project** | Duplicate the project from a specific snapshot                                |

<figure><img src="https://openbrim.atlassian.net/wiki/download/attachments/2101411862/Project%20Revision.gif?api=v2" alt="Revision actions demo"><figcaption><p>Working with revisions</p></figcaption></figure>

***

## Work Log

Add notes to revisions using the work log in the bottom left corner of the graphics window. These notes appear in the revision details.

<figure><img src="https://openbrim.atlassian.net/wiki/download/attachments/2101411862/image-20221110-190546.png?api=v2" alt="Work log"><figcaption><p>Work log entry</p></figcaption></figure>

{% hint style="info" %}
Work log entries help team members understand what changes were made and why.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openbrim.org/openbrim/getting-started/navigation-within-openbrimapp/projects/projects-revisions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.