Hi!

this issue (https://jira.atlassian.com/browse/CONF-22430) is marked as resolved.

However, on our Confluence-Server instance (one version before the latest 6), sharing to groups doesn't work. What am I overseeing?

best.

-sk.

We experienced problems with a large Active Directory in the past. We serve a few thousand users directly, but we also interact with about 10,000 users. We also wanted only some of the AD groups to be seen in the applications. Our remedy was to create our own Organizational Unit in AD where we create groups only for our team's applications. This greatly reduced the load time to display groups. Most of the groups in our OU are mapped to a maintained group outside of our OU. That eliminated most of the overhead for someone to make changes by hand. Having our own OU also stopped the IT department from moving or changing groups, which was causing access to break for the applications. Each day some scripts sync all user and group changes, and send reports to a few people on the team. Going over the reports takes someone less than 5 minutes each morning.

Thanks for the information, Jean-Michel. This is almost what i had feared. Though it looks like you guys are not there yet, i am already worried. We do not want the "Share @ groups" feature to be removed in the future. It's a great feature and we use it a lot. Let's try to find an easy solution that fits everyone but please do not consider of removing this feature.

Thanks for the feedback, we really appreciated it.

We tested the scalability of sharing with huge groups and were comfortable with the performance on large instances. However, we we also debated if we should add more smarts around group sizes (eg, returning the count to show in the dialog or restricting based on a configuration field) to avoid spam. In the end we decided to favour simplicity given that you can already type in any e-mail address in the dialog "staff@mycom.com" and spam.

However, hearing these stories hits home that unlike the e-mail case, the type-ahead for groups makes it even easier. I've opened CONF-33374 to track improvements for configuring group share with large groups. I'm sure we can do something simple to avoid removing the feature but avoiding the spam effects.

We are running into this problem too. We have a company wide email group. When using outlook, only the users allowed can send email to that group. If i try to send email to the company email account, i get a message on outlook saying "You do not have permission to send email to test@atlassian.com). This restriction is set on Active Directory by our IT allowing only few users to send email to the company email account such as executives, people in the administration, HR etc.

We have tried but have not been able to do the same on Confluence. We really love the "Share @ groups" feature on Confluence. What would be nice is a way to implement what we have in outlook on Confluence. I just don't know the best way this can be implemented.

What would be best would be to have several options, e.g.:
1. disable ability to mail to any groups
2. configurable black list – groups which should never appear in any mail-to option or operation
3. configurable size trigger – disable emailing to groups with membership greater than size n

Can you share any thoughts on how to best handle our situation? Or, can you provide any guidance in regards to how other organizations running large instances are handling this?

+1 on this question. We just had a customer share (thinking it meant "give access to" – like in Google docs) to a large group. We stopped the email job after approx 12,000 emails were sent.

We're looking forward to upgrading to 5.4 early this summer. We've started to check out the new features and we had a question about the new "Share with Groups" feature.

We have a bit more than 10,000 users and we have defined several large groups such as schools and departments. We even have a group ("Harvard") that contains all faculty, students, and staff that have signed in to Confluence at least once.

We don't want to give users the ability to send email to these large groups. Our initial investigation shows that we can't easily disable the "Share with Groups" feature while still keeping the ability to share with individual users.

Can you share any thoughts on how to best handle our situation? Or, can you provide any guidance in regards to how other organizations running large instances are handling this?

We are worried about someone taking these specific steps:

• User goes to a page
• User clicks "Share" button
• User selects a large group (such as "Harvard Group")
• User sends email to large group (10000+ individuals)

Thanks,

Danny

Thanks, Jean-Michel. I am watching that page.

apokharel@fncinc.com sorry, no timeline just yet. Keep an eye on the feature request for updates.