I have a use case where there is a restricted confluence page containing sensitive information. Viewership is limited to a select few. This works well to keep the information contained on the page safe.
However, any time the page is updated all watchers get an email of the page contents. This means that the sensitive information has been sent out via email and the safety of it is then dependent on the safety of the email system. This can be more or less secure depending on a lot of factors, but it certainly distributes the information out to a lot of desktops automatically, which is inherently less secure than keeping it contained to the Confluence Wiki.
Is there a way to disable all change/delta notifications and summaries for a specific confluence page or project? Page specific notification exemptions controllable by the administrator is really what I am looking for.
This will uncheck the Notify User Checkbox and hide them to avoid user recheck the checkbox.
Half-jokingly, get a secure email system.
Gmail allows sending email through SSL connections, so do most of email servers, so you can send mail securely to most domains. Concerning the non-safe domains, maybe you could prevent them from setting their email in Confluence?
The last solution is to have a separate instance for your stealth team. If what you're dealing about is so confidential, it may help isolate the data.
Thanks for the Reply Adrien,
1] I hear you about secure email systems. Although, security of data in email is only as secure as the client system that the data ends up on. My goal is to not have the change history of this page distributed to client systems, living on for who knows how long in email cache. While safety on the wire is important, I am mostly concerned with the perpetual record in a client email program like Outlook or Mail.app. This is the kind of user-space data that is a breeze for spyware to mine.
2] Regarding Stealth Instance: I have an on-demand account with many Jira projects and many Confluence spaces. Having a completely seperate account or instance with duplicate accounts and such to prevent dissemination of history for a single page seems like overkill.
This is a question, not a complaint. Is there any way to control this currently in Confluence on-demand settings?
If not I will turn it into a feature request :)
Hi Karen/John, I did hear your question and I only know about workarounds. If we don't get anyone else to provide an alternative answer, it's probably not a feature of Confluence
I don't think you will get lucky with a feature request because it doesn't sound like most Confluence users would benefit from it. However I'm not an Atlassian employee so this is not an official statement and do feel free to seek for comment from Atlassian's product managers.
If you had a download version of Confluence, there would excellent Experts around the world and one of them would certainly be happy to provide a custom solution for you. But I'm afraid they don't have as much control on OnDemand instances.
Best regards and let's hope someone else answers this question.
Thanks everyone for answering last week’s question. The winner of the random drawing from those who commented is: @LarryBrock I’ll contact you separately with your prize details. This wee...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events