> For the complete documentation index, see [llms.txt](https://docs.fylr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fylr.io/for-users/additional-features/change-history.md).

# Change History

Access a records change history in the 3dot menu in the detail view.

Browse through historic versions of a record, see who modified the record how exactly by choosing highlight modes.

### Required Permissions

The following permissions enable users to access the Change History from the fylr detail view.

Available under a users or groups **System Rights > Frontend Features**.

Permission **Access Change History**:

* Allows users to see change history
  * If only view permissions for record are present, Usernames are not shown in change history
  * If edit permissions are present usernames are shown in change history

Permission **Access Change History with Users**:

* User always has access to change history **and** usernames

#### Restore Versions

If a user has the permissions to **edit the record and access the change history**, this user can restore historic versions by opening the change history while editing in the detail view.

After restoring, saving is still required.

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fylr.io/for-users/additional-features/change-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.