Demo
A client page where every change is reviewed
One client page, seen by three people with different roles. Each role sees only the sections it is allowed to see, and an update reaches the page only after a second person approves it.
This is a simulation. The client, the people and every note are invented. No AI model runs on this page, nothing you do leaves your browser or is kept, and reloading the page starts again.
Signed in as
Try this
- As Maple, press Approve on Q-1. Staff can suggest updates but cannot approve them.
- Switch to Rowan, and account notes appear. Then press Approve on Q-2, which Rowan sent: refused, nobody approves their own.
- Switch to Juniper, and money terms appear. Now press Approve on Q-2 and watch the page and the audit trail change.
Client page: Bramble
Day 12
Bramble, a garden supply shop. Two sections are hidden for your role.
At a glance
Seen by: Everyone
Garden supply shop with one store and a small online shop. Client since day 3.
Version 1
Hidden for your role. Everyone.
Services
Seen by: Everyone
Two social posts a week, a monthly report and the local search listing.
Version 1
Hidden for your role. Everyone.
Likes and dislikes
Seen by: Everyone
Likes real photos of the store. Dislikes jargon in captions.
Version 1
Hidden for your role. Everyone.
Account notes
Seen by: Account managers and leadership
Version 1
Hidden for your role. Account managers and leadership.
Money terms
Seen by: Leadership only
Version 1
Hidden for your role. Leadership only.
Review queue
Updates wait here. Approvers are account managers and leadership, and an update only changes the page once someone other than its sender approves it.
Q-1, Likes and dislikes, from Maple, based on version 1
Likes short captions with one photo. Dislikes jargon in captions.
Waiting for an approver
Q-2, an update to a section your role cannot see
Waiting for an approver
Suggest an update
You can only pick sections your role can see. Text that looks like a password or key is refused.
Audit trail
Every suggestion and decision, oldest first. An approval writes the change and its line here in the same step.
- Day 3: Bramble imported with 5 sections, each at version 1.
- Day 11: Maple suggested Q-1, an update to Likes and dislikes.
- Day 11: Rowan suggested Q-2, an update to a section your role cannot see.
What the demo shows
- Visibility belongs to the data. Each section has an audience. A section your role cannot see is hidden on the page, and the queue, the form and the audit trail never show its name or text either.
- Every change is reviewed. A suggestion waits in the queue with the version it was based on. The page changes only when an approver accepts it.
- Nobody approves their own. Staff can suggest but not approve, and an approver cannot accept an update they sent.
- No lost edits. If a section changed after an update was suggested, approving the older update is refused, so nobody overwrites a newer change.
- A full audit trail. Each suggestion, approval and rejection is written down, and an approval changes the page and writes its line in one step.
- No logins on client pages. Text that looks like a password or key is refused when it is sent and again at approval.