Hi everyone,
You ask fifty people to confirm the updated security policy. By the next morning there is a list: who has confirmed, and who hasn't. Then the questions start that have nothing to do with the policy. Can the rest of the company see that list? Who keeps the request going while you're on leave? And for the one document where the names themselves are sensitive, how do you keep the list to yourself?
Read & Confirm for Confluence records who has confirmed a Confluence page. Every request answers those three questions the same way, and this article walks through the rules: everyone on the site can see a request, only two kinds of people can change it, and a request can be private from the moment it's created.
🗂 Everyone can see the list. Two kinds of people can change it.
The dashboard has three tabs. My Requests holds the requests you created. Managed holds the ones someone handed to you. All Requests holds every request on the site. Each row shows who created it, so you can still find a request after the person who made it has changed teams.
Open any request from All Requests and you see what the creator sees: the progress, the note to readers, the managers, and the table of names with status, page version, and confirmation time. Export works for everyone. What's missing is the action row. Reminders, Mark complete, Archive, Delete, + Users, Remove, and + Managers appear only for the creator and the managers, and the server checks the same rule before it changes anything.
So the default is: visible to the whole site, changeable by the people named on the request.
👥 Handing the request to a colleague
A request can have up to 10 managers. A manager has the creator's powers in full. The Add managers dialog puts it in one line: Managers can update this request like the creator: edit users, reminders, status, and delete. There's no read-only manager.
Two things don't move. The creator is fixed: the creator can't be removed from the request and can't be swapped for someone else. And archiving freezes the list: no manager goes on or off until the request is restored. A completed request can still take new managers.
Requests handed to you show up under Managed. The practical rule is to name a manager while the creator is still around. If the creator's Atlassian account is closed and nobody else was named, nobody is left who is allowed to change the request.
🔒 When the names are the sensitive part
Some lists shouldn't be open to the whole site: who has been briefed on a reorganization that isn't public yet, or which managers have read a pay-review procedure. For those, tick Private when you create the request. The hint under the checkbox says what it does: Only you and managers can see who confirmed.
Three things change:
- The names stay with the creator and the managers. The table of names and the CSV export stop there.
- The people on the request still confirm as usual. They see the request on the page and in My Confirmations, and they see their own status. They don't see who else has confirmed.
- Everyone else doesn't see the request at all. It's left out of All Requests, and the confirmation box on the page shows nothing for them.
Comments that put names on the page are off by default for a private request. The assignment comment that @mentions assignees and the deadline reminders both reveal who 's on the list, so the request skips them unless you turn them on in the same dialog. With them off, people find the request in My Confirmations and on the page itself.
Private is available for requests sent to named people, not for "all viewers" requests, and it can only be set when the request is created. There is no switch afterwards. The only way to change it is to delete the request and create a new one, and the confirmations already recorded don't carry over.
🔗 Marketplace listing:
https://marketplace.atlassian.com/apps/1138072457/read-confirm-for-confluence
Where does your team keep the list of who has read a policy today: on the page itself, in a spreadsheet, or in someone's inbox? Comments welcome.
