• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Currently I am able to share a page with certain users or e-mail adresses.
      It would be nice if I was able to share a page with a whole group (like it is possible with the "Mail Page" Plugin).

            [CONFSERVER-22430] Share pages with groups

            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.

             

            Stefan Knecht added a comment - 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.  

            Doug added a comment -

            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.

            Doug added a comment - 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.

            Adhip Pokharel added a comment - - edited

            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.

            Adhip Pokharel added a comment - - edited 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.

            JeanA added a comment -

            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.

            JeanA added a comment - 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.

            Adhip Pokharel added a comment - - edited

            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.

            Adhip Pokharel added a comment - - edited 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

            Carter Snowden added a comment - 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.

            Chad Barnes added a comment - 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

            Danny Brooke added a comment - 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.

            Adhip Pokharel added a comment - Thanks, Jean-Michel. I am watching that page.

            JeanA added a comment -

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

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

            Thanks, Jean. This might be too early to ask but any timeline on when @ mention for groups will be implemented?

            Adhip Pokharel added a comment - Thanks, Jean. This might be too early to ask but any timeline on when @ mention for groups will be implemented?

            JeanA added a comment -

            We are trying to track down why the plugin upgrade isn't working for everyone. Use the manual jar upload for now.

            apokharel@fncinc.com @ mention for groups that is coming up next. Track it in https://jira.atlassian.com/browse/CONF-23015.

            JeanA added a comment - We are trying to track down why the plugin upgrade isn't working for everyone. Use the manual jar upload for now. apokharel@fncinc.com @ mention for groups that is coming up next. Track it in https://jira.atlassian.com/browse/CONF-23015 .

            Thanks John & Jean. We got the same error when we tried to upgrade the Share page add-on. We did a manual workaround as well by downloading the jar file and uploading it.

            My next question is about @ mention with groups. Do you guys have any plans towards that?

            Adhip Pokharel added a comment - Thanks John & Jean. We got the same error when we tried to upgrade the Share page add-on. We did a manual workaround as well by downloading the jar file and uploading it. My next question is about @ mention with groups. Do you guys have any plans towards that?

            Upgraded to 5.1.5 last night and this looks like it's now fixed.

            Internal Support added a comment - Upgraded to 5.1.5 last night and this looks like it's now fixed.

            I tried to update the Share Pages plugin after the Confluence Update to 5.1.5. This time it worked without any problem.

            Michael Schlueter (secunet) added a comment - I tried to update the Share Pages plugin after the Confluence Update to 5.1.5. This time it worked without any problem.

            JeanA added a comment -

            davidrr great question. We haven't limited the group size, but filter out the built-in groups (eg, confluence-admins and confluence-users) from the group options for exactly the reason you mentioned. When mail is sent, the request is handled asynchronously on the server so that it doesn't timeout. We've tested large groups 1000+.

            JeanA added a comment - davidrr great question. We haven't limited the group size, but filter out the built-in groups (eg, confluence-admins and confluence-users) from the group options for exactly the reason you mentioned. When mail is sent, the request is handled asynchronously on the server so that it doesn't timeout. We've tested large groups 1000+.

            David Yu added a comment -

            Can we can clarification on how the feature behaves with large groups? For example, someone accidentally types in "confluence-users" and it queues up a message for 5,000+ users? Is there a share group size limit?

            David Yu added a comment - Can we can clarification on how the feature behaves with large groups? For example, someone accidentally types in "confluence-users" and it queues up a message for 5,000+ users? Is there a share group size limit?

            schlueter.michael, rrollins, I gave both 5.13 & 5.1.4 a quick test then myself and was able to upgrade, so I guess it's either an intermittent issue or something specific to your instances. You might (along with pawnyc) like to raise a ticket with http://support.atlassian.com to investigate it.

            John Masson added a comment - schlueter.michael , rrollins , I gave both 5.13 & 5.1.4 a quick test then myself and was able to upgrade, so I guess it's either an intermittent issue or something specific to your instances. You might (along with pawnyc ) like to raise a ticket with http://support.atlassian.com to investigate it.

            I've been getting that error a lot recently as well when I have been updating plugins. My work-around has been to just download the actual jar files from the atlassian marketplace listing and then do a manual upload through the upm page.

            Paul Wieckiewicz added a comment - I've been getting that error a lot recently as well when I have been updating plugins. My work-around has been to just download the actual jar files from the atlassian marketplace listing and then do a manual upload through the upm page.

            +1 to the "An error was encountered while updating this add-on", my version of Confluence is 5.1.4.

            Russ Rollins added a comment - +1 to the "An error was encountered while updating this add-on", my version of Confluence is 5.1.4.

            I have a problem with the update of the Share page system add-on. Our current version is 2.0.8 (Confluence 5.1.3).
            If I try to update the Share Page Add-on, I get a generic error message "An error was encountered while updating this add-on.".
            Is this a known problem?

            Michael Schlueter (secunet) added a comment - I have a problem with the update of the Share page system add-on. Our current version is 2.0.8 (Confluence 5.1.3). If I try to update the Share Page Add-on, I get a generic error message "An error was encountered while updating this add-on.". Is this a known problem?

            Matt added a comment -

            Shares pages and blogs with groups is now available for both OnDemand and Download customers. See the following post for more details:

            http://blogs.atlassian.com/2013/07/introducing-group-sharing-get-everyone-in-one-fell-swoop/

            Using OnDemand?

            You’ve been auto-updated – log in and start sharing with groups today.

            Using Confluence Download?

            Confluence 5.1 and above: Update to the latest version of the Share Page system add-on via the Universal Plugin Manager in the Confluence Admin console.

            The new version of this plugin will be bundled with Confluence 5.2 which is scheduled for release in early August.

            Matt added a comment - Shares pages and blogs with groups is now available for both OnDemand and Download customers. See the following post for more details: http://blogs.atlassian.com/2013/07/introducing-group-sharing-get-everyone-in-one-fell-swoop/ Using OnDemand? You’ve been auto-updated – log in and start sharing with groups today. Using Confluence Download? Confluence 5.1 and above: Update to the latest version of the Share Page system add-on via the Universal Plugin Manager in the Confluence Admin console . The new version of this plugin will be bundled with Confluence 5.2 which is scheduled for release in early August.

            John Alton added a comment -

            I'm following this thread because I have the same need.

            Here to report that I AM able to share a page with an Active Directory group. Can provide additional details if you'd like.

            John

            John Alton added a comment - I'm following this thread because I have the same need. Here to report that I AM able to share a page with an Active Directory group. Can provide additional details if you'd like. John

            infrastructure1, stevenp, if you could replicate with support that would be ideal, then they can get a bug report with the details raised.

            This will be bundled in 5.2 as part of the release.

            John Masson added a comment - infrastructure1 , stevenp , if you could replicate with support that would be ideal, then they can get a bug report with the details raised. This will be bundled in 5.2 as part of the release.

            Steven Parsons added a comment - - edited

            The same thing appears to be happening with my set up as well. If I manually create a group within Confluence it will send to the group of people, If I use the groups replicated from AD it appears not to send.

            Steven Parsons added a comment - - edited The same thing appears to be happening with my set up as well. If I manually create a group within Confluence it will send to the group of people, If I use the groups replicated from AD it appears not to send.

            Is this working for everyone? I'm synchronising 2 OU's from my Active Directory (1 for users and 1 for distribution groups) and whilst adding the plugin now detects that these groups exist (auto-complete works) it doesn't appear to send to everyone in that group. Happy to replicate this with support to show the issue.

            Also, is this the way the fix will be rolled into 5.2 (via plugin) or will it be baked into the release?

            Internal Support added a comment - Is this working for everyone? I'm synchronising 2 OU's from my Active Directory (1 for users and 1 for distribution groups) and whilst adding the plugin now detects that these groups exist (auto-complete works) it doesn't appear to send to everyone in that group. Happy to replicate this with support to show the issue. Also, is this the way the fix will be rolled into 5.2 (via plugin) or will it be baked into the release?

            Uwe Kluge added a comment -

            A really good news would be a backwards compatible version for CF 4.3!
            So all user that have to stick with the older version are still locked out from this very basic functionality...

            Uwe Kluge added a comment - A really good news would be a backwards compatible version for CF 4.3! So all user that have to stick with the older version are still locked out from this very basic functionality...

            For those running 5.1, we've made a backwards compatible version available that works with 5.1 - 5.1.4. You should be able to update to it via the UPM or download it from the Marketplace.

            John Masson added a comment - For those running 5.1, we've made a backwards compatible version available that works with 5.1 - 5.1.4. You should be able to update to it via the UPM or download it from the Marketplace .

            @aleksandar.borojevic Please, vote JRA-33735 JRA-33736

            ChangJoon Lee added a comment - @aleksandar.borojevic Please, vote JRA-33735 JRA-33736

            I share the same opinion like Lee. It would be very useful to have this feature in Jira as well.

            Aleksandar Borojevic added a comment - I share the same opinion like Lee. It would be very useful to have this feature in Jira as well.

            This feature should be expanded to JIRA, too!

            ChangJoon Lee added a comment - This feature should be expanded to JIRA, too!

            Can't wait to see this!

            ChangJoon Lee added a comment - Can't wait to see this!

            Thanks, Jean. I think i have already added a comment there.

            Adhip Pokharel added a comment - Thanks, Jean. I think i have already added a comment there.

            JeanA added a comment -

            apokharel yeah, mentions support for groups is being tracked in https://jira.atlassian.com/browse/CONF-23015

            JeanA added a comment - apokharel yeah, mentions support for groups is being tracked in https://jira.atlassian.com/browse/CONF-23015

            Adhip Pokharel added a comment - - edited

            Excited about this.Thank you. Can this be included in the @mention as well?

            Adhip Pokharel added a comment - - edited Excited about this.Thank you. Can this be included in the @mention as well?

            This is almost too good to be true!

            Joe Westcott (ITDP) added a comment - This is almost too good to be true!

            MJP added a comment -

            Thank you, I appreciate it.

            MJP added a comment - Thank you, I appreciate it.

            very happy that this has arrived

            Tobias Leenaert added a comment - very happy that this has arrived

            Agreed, a BIG thank you!

            Ethan Foulkes added a comment - Agreed, a BIG thank you!

            Matt added a comment -

            Way to go jmlemieux!

            Matt added a comment - Way to go jmlemieux !

            JeanA added a comment -

            This will be in OD soon (week or so) and is bundled in 5.2. It relies on new API for quickly searching for groups, and thus can't be back-ported to earlier releases.

            JeanA added a comment - This will be in OD soon (week or so) and is bundled in 5.2. It relies on new API for quickly searching for groups, and thus can't be back-ported to earlier releases.

            This makes sense. When I am able to share with single users, why not with groups? Since we are running many spaces for large user groups it is not very practicable to put in 50 or more userids into the share field.

            Stefan Baader added a comment - This makes sense. When I am able to share with single users, why not with groups? Since we are running many spaces for large user groups it is not very practicable to put in 50 or more userids into the share field.

            can you provide an add-on for 4.3 please?

            Hans-Peter Geier added a comment - can you provide an add-on for 4.3 please?

            BillA added a comment -

            Mid/late July is the current plan.

            BillA added a comment - Mid/late July is the current plan.

            Susanne added a comment -

            "Jean-Michel Lemieux [Atlassian] added a comment - 08/Apr/13 8:30 AM
            It will be in 5.2 and in OnDemand (sooner). We don't have plans to backport to 5.1."

            When will Confluence 5.2 be released?

            Susanne added a comment - "Jean-Michel Lemieux [Atlassian] added a comment - 08/Apr/13 8:30 AM It will be in 5.2 and in OnDemand (sooner). We don't have plans to backport to 5.1." When will Confluence 5.2 be released?

            really missing this basic function

            Tom Birch Hansen added a comment - really missing this basic function

            This feature tremendously influences user acceptance. Outlook should not be superior over confluence in sharing your confluence pages! Since Atlassian rocks - please let us hear the full scale with group shares.

            Bernd Mayer added a comment - This feature tremendously influences user acceptance. Outlook should not be superior over confluence in sharing your confluence pages! Since Atlassian rocks - please let us hear the full scale with group shares.

            a Must have for me, too.
            A Must Have for getting this feature added to 4.3, too!

            This great Mail plugin which was given to us earlier as a work-around, has been depreciated on Confluence 4.x without replacement (as this request here hasn't been delivered yet). How can Atlassian depreciate existing functionality but not complete the functionality like this here at the same time?

            Hans-Peter Geier added a comment - a Must have for me, too. A Must Have for getting this feature added to 4.3, too! This great Mail plugin which was given to us earlier as a work-around, has been depreciated on Confluence 4.x without replacement (as this request here hasn't been delivered yet). How can Atlassian depreciate existing functionality but not complete the functionality like this here at the same time?

            JeanA added a comment -

            What stevenp said is accurate. If the groups are sync'd into Confluence from your directory server, then they will show as they will also now in the restrictions dialog.

            JeanA added a comment - What stevenp said is accurate. If the groups are sync'd into Confluence from your directory server, then they will show as they will also now in the restrictions dialog.

            Good question. I expect the groups from AD will work, currently you can propagate them into CF so I expect you will be able to share using them.

            Steven Parsons added a comment - Good question. I expect the groups from AD will work, currently you can propagate them into CF so I expect you will be able to share using them.

            Will this display groups that are from Active Directory/LDAP or only local groups?

            Evan Overby added a comment - Will this display groups that are from Active Directory/LDAP or only local groups?

            Thanks for the update Jean-Michel.

            Steven Parsons added a comment - Thanks for the update Jean-Michel.

            JeanA added a comment -

            It will be in 5.2 and in OnDemand (sooner). We don't have plans to backport to 5.1.

            JeanA added a comment - It will be in 5.2 and in OnDemand (sooner). We don't have plans to backport to 5.1.

            Will this fix be included in the next download release for 5.1?

            thanks,

            Steven Parsons added a comment - Will this fix be included in the next download release for 5.1? thanks,

              jmlemieux JeanA
              48ff0be30bda Stephan Haslinger
              Votes:
              184 Vote for this issue
              Watchers:
              142 Start watching this issue

                Created:
                Updated:
                Resolved: