Share confluence With customers

[naama lev]

Hello Experts, 

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?

1. model collaboration suggestions
2. what is private / what is public

Thanks

Naama

[Gorka Puente [Comalatech] · Accepted solution]

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!

Regards,

Gorka

[Filip Callewaert]

Hi Gorka, can people who you share the page with also comment on the page?

[Gorka Puente [Comalatech]]

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!

[Ricardo Morales]

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?

Thanks. 

[Joe Xie]

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.

[naama lev]

Thanks for that :)