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
Our company would like to share our confluence instance with our customers - so we could work together on documents and communicate on project deliverables, decisions, ect.
Can you please share your experience with me?
Hi Ricardo Morales,
You can share pages and attachments outside Confluence with Comala Share It. Your customers can access the pages you select for them, and you don't need to create additional users.
Disclaimer: My company, Comalatech, is the vendor of Comala Share It
Let us know what do you think!
Hi @Filip Callewaert, it's not currently possible, but we do have an internal feature request for doing so. I've created a support ticket in https://comalatech.zendesk.com/ to keep the discussion going!
Hello. We are a small team and we are looking for something similar. We want to share some content with our customers, so they can see what we are doing for them, but we cannot give public access to that content because any one would be able to see it. We want that one customer can see only what we are developing for him, but we don't want to spent our confluence licenses with such customer. is there any way to do that?
there's a blogpost on the atlassian website that detail one way you can collaborate with confluence http://blogs.atlassian.com/2013/04/how-to-run-effective-meetings-with-confluence/ - perhaps that will give you some inspiration? Also, with regard to specifications for projects, we internally use https://confluence.atlassian.com/display/DOC/Product+Requirements+Blueprint quite a lot, along with decisions blueprints https://confluence.atlassian.com/display/DOC/Decisions+Blueprint to make sure decisions are grouped together for easy access and reading. The model is (for a software product/feature) to first gather the requirements by sharing the page around with the stake holders, and allowing them to edit/add things they want. During this time, many meetings may happen, and the results recorded. Then finally, a decision page to solidify the choice(s). Then the spec is shared around the team. As for private/public, that depends on your organization and whether you want the customer to have deeper access or just present a polished set of pages to them.