Is anyone out there using 2 instances of Confluence on Demand one to develop tech doco and then another instance to publish it for customers?? So one instance would be our internal site with draft versions etc and the other instance would contain the signed-off doco and be accessible to customers?
The reason we are thinking of doing this is to simplify the whole permissions things:) pros? cons?
IMO permissions in Confluence are pretty damn simple if you avoid using page restrictions. This is a very simple scenario you are talking about compared to organisations with complex departmental relationships. Imagine an organisation with 20 departments, each of which have various client/vendor type relationships with one another all sharing the same Confluence instance quite happily. This is what Confluence was built to support. If you fragment it, I suspect you wont be able to leverage some of the social features in Confluence as effectively. Your technical team wont be engaging as directly with your clients to allow them to improve your product(s) and your client relationship as fluidly as they otherwise might. I hope that made sense, it's just my gut feeling.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs