# Every change, with a name on it.

> The audit log lists everything that happened at your publication, and who did it: staff, readers, agents and PixelGlass. Notifications show what matters.

Settings › Audit log keeps every event at your publication for a year: a post published, a role changed, a theme switched, a reader who signed up. **When an agent did it, the log names the person and the app.** Notifications show each role the events it needs.

## By hand, in the admin

1. As the owner or an admin, open **Settings › Audit log**. The newest events come first, fifty a page.
2. Narrow it with **Area**, such as Posts and pages or Staff and agents, and with **Who**: one staff member, Readers or PixelGlass.
3. A change made through an agent reads as the person, through the app they connected.
4. For what needs you, open **Notifications** in the navbar. Each role sees its own events from the last 90 days, and opening the list marks them read.

## With your agent

> When did the post “Ten years of the harbour market” go out, and who wrote it?

> Show me the history of the site pages, and bring back the pricing page as it was on Tuesday.

The tools it calls: `list_posts`, `get_post`, `site_pages_history`, `restore_site_pages`.

No tool reads the audit log. An agent reads a post's facts and a site page's history, and your own code reads the log as JSON with a staff key from Settings › API.

## Examples

- **A post that changed overnight.** An admin finds a headline she did not write. **The log says a colleague's agent changed it at 2 a.m.**, and the post's history takes it back.
- **Who joined the team.** The owner of a magazine checks the Staff and agents area each month: every invitation, every person who joined and every role changed.
- **An inbox for each role.** A writer on the team opens Notifications to the events her role needs. Who joined the staff stays with the admins.

## Questions

### Does PixelGlass have an audit log?

Yes. Settings › Audit log lists every event at the publication, newest first, with who did it: a staff member, a reader, an agent working as a person, or PixelGlass itself.

### Who can read the audit log?

The owner and the admins. Every role has Notifications, which shows the events that role needs.

### How long does PixelGlass keep events?

An event stays in the audit log for one year. Notifications look back 90 days.

### Can I see what an AI agent changed?

Yes. A change through an agent is in the log under the person who connected it, with the name of the app. A post's own history keeps each version, ready to restore.

### Can I read the audit log from code?

Yes. With a staff key, GET /pixel/settings/audit-log.json returns the same events, filtered by area and by who, fifty a page.

## See also

- [Invite your team](https://pixelglass.co/guides/invite-your-team): Invite writers, editors and admins to your PixelGlass publication by email, each with a role that sets what they may do. No price per seat.
- [Read your notifications from code](https://pixelglass.co/guides/read-your-notifications-from-code): New members, comments, paid plans, sends and agents' posts, as JSON with a staff key. Every event of the audit log too, for owners and admins.
- [Restore an earlier version](https://pixelglass.co/guides/restore-an-earlier-version): Post history keeps the last 50 versions of every post. See what changed, who changed it, and restore any version in the editor.
- [Developer API](https://pixelglass.co/features/developers): Read your site as JSON, sync members from your app, sign readers in with your own accounts, and run it all from an agent. Webhooks are coming soon.
- [MCP server](https://pixelglass.co/features/mcp-server): Every PixelGlass site is an MCP server with 68 tools. Claude, ChatGPT, Cursor and more write posts, design themes and run your publication.
- [Every guide](https://pixelglass.co/guides)
- [Pricing](https://pixelglass.co/pricing): every feature on every plan, 14 days free
- [Create your site](https://pixelglass.co/signup)