Hi @Franz ,
I think you've spotted a real limitation, and it's not really a Comala bug, it's a consequence of how the app works on top of Confluence. Comala adds a permission layer on the page view, but the underlying versions still live in Confluence's normal storage. So anything that reads directly from that storage (page history, watch notifications, exports, search API...) sees the raw content and bypasses the workflow rules.
There's no single switch that closes all these holes at once, but you can layer a few things to get much closer:
Restrict the pages themselves. Combine Comala with Confluence's native page restrictions. Set the draft/unpublished pages so only the authors and reviewers have view access at the Confluence level. This is the strongest fix because it removes the content from history, notifications and search for everyone else, not just the Comala UI. Comala has automation actions that can apply and remove restrictions automatically as the page moves through the workflow states, so you don't have to do it manually every time.
Turn off "include page content" in notifications for that space, or better, disable watching at the space level. In Space settings > Mail, you can strip the content out so watchers only see a link, which then respects permissions when clicked.
Consider splitting spaces. For anything truly confidential, a dedicated space with tight permissions is safer than trying to hide drafts inside a mixed space. Publish the finalized version into the shared space when it's ready.
PS: don't rely on Comala alone for confidentiality. Use it for the workflow, and use Confluence page restrictions for the actual security.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.