You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We currently have a datacenter solution for our Confluence instance, but we're exploring the possibility of migrating to Confluence Cloud hosting. One of the main reasons for considering a cloud solution is to improve availability and ease of maintenance. However, we have some concerns related to data accessibility and would like to discuss a potential licensing change with the community.
Our usage of Confluence revolves around creating runbooks and how-to guides for both our employees and clients, particularly during internal issue resolutions. Some of these instructions contain sensitive data. In our datacenter setup, we've been able to manage access effectively by configuring spaces to allow anonymous access when necessary. These documents can be accessed through our internal network and VPN.
However, our challenge with moving to Confluence Cloud lies in the fact that documents become accessible to anyone with internet access. Although there is an option to restrict access based on certain IP addresses, this approach doesn't align with our environment's requirements and accessibility.
We're interested to know if Atlassian has considered or discussed changing the cloud licensing model to distinguish between read-only and editing access. We believe this could be a beneficial solution for companies like ours, seeking to adopt cloud solutions while ensuring certain pages remain private and secure.