Seeing who changed a blueprint

Every change to a workspace's blueprints is recorded with who made it and how, and the workspace's owners and admins read it in the audit log.

Every change to a blueprint is recorded with who made it and how. Workspace owners and admins find each one in the workspace's audit log, in the Admin tab of the dashboard (see Workspaces, accounts, and limits).

What the audit log shows

A row for each change to one of the workspace's blueprints:

• an edit to the file or to its page
• a change to who can see it, or to how it is listed
• publishing approved on a card (see Blueprints: sharing a setup someone else can run)
• taking it down
• attaching, showing or removing a live example

A change an agent made names the agent, and the person it was working for when there was one, so "the agent edited it" and "you edited it" read differently. An agent working on its own schedule shows as the one who made the change.

Changes Bolter makes to your blueprint are there too: a staff edit, featuring it in the gallery, offering it to people who are new to Bolter, listing it in the gallery or declining to after a review, and marking it as built by Bolter. A blueprint brought in by Bolter staff, or a review copy installed to test one, shows up in the workspace it landed in.

What it does not show

The log says what kind of change it was and which blueprint, never the file itself. A draft can hold something you later took out, and the audit log is readable by every admin of the workspace.

Bolter keeps every earlier version of the file. Bolter staff can read that history when you ask for help with a blueprint, for example to find out what changed between two versions or to bring back something that was lost.