Running a publication

Every change,
with a name on it.

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.

Create your site – free Start from your agent
Say it to your agent

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

  • list_posts
  • get_post
  • site_pages_history
  • restore_site_pages

Two ways to do it.

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

In Claude, ChatGPT or your editor

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.

For example

  • 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, answered

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.

Next, try

Every guide →

The features behind it

Every feature →

Every feature on every plan

Start your publication
today.

Plans from $9 a month. No platform fee on what your readers pay.

Create your site – free Start from your agent

14 days free. Have a site? Sign in