# Read your site’s history

This article explains how to read your site’s history. It records every action with its author and date: publications, exports, members, settings, content and design. You will be able to open it, read its lines and filter them.

## Before you start

- The **History** button appears only to site administrators. An editor, an author or a contributor does not see it and cannot read the history.
- A line stays in the history for twelve months, then it is deleted.
- Neither you nor the Lovely Render team can edit or delete a line.

## Open the history

1. In the **Dashboard**, find the site’s card.
2. At the bottom of the card, click **History**. The **History** panel opens on the side. The most recent line comes first.
3. To see only one kind of event, choose a value in the **Category** list. **All** shows every line.
4. To go back in time, click **Next**. **Previous** returns to more recent lines.

The panel shows fifty lines per page.

![The History panel of atelier-sauge.fr: the Category list set to All, then the columns Date, Who, What happened and Environment. The lines show an edition of the Privacy policy put online, a finished publication, content edited by Julie Garnier via Claude, an invitation and the connection of the Claude agent.](https://static.lovelyrender.com/uploads/2026/10/242-equipe-historique.png)

## Read a row

| Column | Content |
| --- | --- |
| **Date** | The day, with the time below it. |
| **Who** | The name of the person who acted. |
| **What happened** | The category in small caps, then the event in one sentence, for example **Edited the page “City gardens”**. |
| **Environment** | **Staging** or **Production**, when the distinction matters. A dash otherwise, for example for an invitation. |

On a phone, each line becomes a block: the date and the environment at the top, then the person, then the event.

| Displayed name | Meaning |
| --- | --- |
| A name, for example “Claire Roussel” | The person acted themselves. A person from the Lovely Render team also appears under their name, here and not in the **Members** panel. |
| A name followed by “via” and an AI, for example “Julie Garnier via Claude” | The AI that this person connected acted for them. The name of the AI is the one recorded when the person authorized it. |
| **System** | Nobody clicked. It is a scheduled action, such as scheduled content that appears at its time or the trash emptied after thirty days. |
| **Deleted account** | The person’s account no longer exists. |

## Filter by category

| Category | Events |
| --- | --- |
| **Published** | A publication to Production and its result, a restored version of the site and the Production copied back into Staging. |
| **Data** | A form’s requests exported with their count, a deleted request and the exported site with the size of the archive. |
| **Access** | An invitation sent, canceled or accepted, a member added, changed or removed, an AI connected, its rights changed or removed and a preview link created or revoked. |
| **Settings** | The general settings, a redirect, the sending of a form’s requests to another tool, a linked Google or Bing account and the structured data. |
| **Content** | A page, a post, an entry or a legal document created, edited, moved to the trash, restored or deleted, a linked translation, a content import and an edition of a legal document put online. |
| **Design** | A Design system setting, a registered style, a font, a brand image, an icon or an animation added, changed or removed and a catalog design applied. |
| **Structure** | A content type or a field saved or deleted, a type disabled, re-enabled or returned to its original version, an imported package of types, a content template, a language added, removed or set and translated labels. |
| **Media** | A media file added or deleted. |
| **Fleet** | The Lovely Render team’s actions on your site: a plan change, a suspension or a reactivation. |

## Know what the history does not keep

- The content of the actions. A line says that a page was edited. What changed stays in the page’s revisions, which you open in the editor. Another line says that 412 requests were exported but does not contain any of those requests.
- The editor’s automatic saves while you write. Each click on **Save** makes one line.
- The emails sent by the site.
- Logins to your account.
- Actions with no effect, such as an invitation that was resent or expired.

**Note:** A deleted request cannot be recovered through the history. The line says who deleted it and when, but not its content.

## Understand why your site cannot erase the history

The history is kept at Lovely Render with your dashboard, outside your site. Your site writes each event to it through a signed link, but can neither read it back nor erase it. A person who gained access to your site could not erase the trace of their visit.

## Have an AI read the history

An AI connected to your site always rereads its own lines. It can then tell you what it changed yesterday, page by page.

For it to read the whole history of the site, including your lines and those of your collaborators, grant it the **Read the history of the site** right. This right is offered only to site administrators. [Connect your AI](https://lovelyrender.com/documentation/connect-ai/) explains how to grant it.

**Note:** A change enters the history a moment after it is made. A publication enters it once it is finished. If the AI rereads right away, the latest line may still be missing.

## Export the history

The archive that an owner downloads contains the whole history in the file `history.csv`. Each action takes one line. [Take your site with you](https://lovelyrender.com/documentation/export-your-site/) explains how to request it.

## See also

- [Invite a member and choose their role](https://lovelyrender.com/documentation/invite-member/)
- [Connect your AI](https://lovelyrender.com/documentation/connect-ai/)
- [Understand your site’s security](https://lovelyrender.com/documentation/site-security/)