We have deployed confluence internally behind our firewall but we have requirements from departments to create spaces where customers or 3rd party people can document and talk on products. What are the best practices for doing something like this ?
I see following options :
1. Open up the internal server to external people but use permissions on the spaces, here we risk that internal people forget to set correct permissions and the content get's out to everybody.
2. Deploy another instance only for external people.
What do you do in your organization ?
It's possible to have your existing shared externally, but as you mentioned it's important that there is strong access control performed by the admins. I would give the default confluence-users group the baseline rights that you would use for external users, and create extra groups for your company staff.
One thing to remember is that you'll have to use the same Confluence base url to be accessible for both internal and external customers.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Community, Jessica here from the Confluence Product Marketing team! July’s community challenge is all about sharing pictures — and as an extension of our first post on what ...
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