Diary adds no permission system of its own. Everything comes from Confluence's own page permissions, which means there is nothing new to configure and nothing new to audit.
Who can do what
|
Action |
What you need |
|---|---|
|
Read the entries |
Permission to view the page. Anyone who can see the page sees the diary. |
|
Add, edit, or delete an entry |
Permission to edit the page — the same permission you would need to open the page editor. |
What read-only viewers see
A user who may view the page but not edit it sees the entries and nothing else: no editor prompt, and no Edit or Delete button on any entry. There is no control on screen that could only fail.
📷 Screenshot: read-only-view.png — the same diary seen twice, side by side or as two stacked images: once as a user with edit permission (prompt at the top, Edit and Delete buttons on each entry) and once as a read-only viewer (entries only, no controls anywhere). The comparison is the whole point, so keep the entries identical between the two.
On an empty diary they are simply told that no entries have been written yet, rather than being invited to write the first one.
Entries you did not write
Page edit permission is the whole test — there is no separate "your own entries only" mode. Anyone who may edit the page may edit or delete any entry in the diary, exactly as they could by opening the page editor and changing the table by hand.
Every such change is a page version, so page history always shows who changed what.
Restricting who may write in a diary is therefore a matter of restricting who may edit the page. Use Confluence page restrictions exactly as you would anywhere else.
Turning writing off entirely
To stop everyone adding entries while keeping the existing ones readable, set Position Of Editor to Hidden. That removes the new-entry editor for all users.
Treat this as a display choice rather than a security control: someone with page edit permission can still change the entries through the page editor.
Every write is made as you
When you save an entry, the app updates the page as your own Confluence user. Confluence applies your permissions to that write, so the app cannot change a page you could not have changed yourself, and the new page version records you as its author.