I just entered a request CWD-5549 for this feature to be added to the Server version.  So Mike Rocheleau please vote for it.  Don't know why this implemented in all their versions and we have to request it features separately for each version...

Can we ever expect this to make it to Server, not just Data Center?  This is a really useful feature we'd love to have.

Hello @kangil.ahn,

I don't think it would be cool to advertise another company's product here.

Hey, Atlassian, I just wanted you to know that the choice by Atlassian to require a Data Center license for this feature (along with some other reasons) has led to my company deciding to move to a different SSO tool. This is a long term decision, but just so you know, you literally lost instead of gained a customer based on your short term thinking.

it works.

My crowd data Center has many user directories. A Group may be defined in different user directories.

If I delegate the Group Administration to  an user, I expect that the user will be able to see his Profile and the menu point "Groups" in order to list all Groups which he may administer.

My Problem as crowd user  as well as crowd admin the menu point "Groups" is missed.  

@Marek Radochonski It's great to see you here to assist Dourget. However as a senior Product Manager, are you able to please speak to all the people who have commented on this ticket (like you asked in the update) to give feedback on the Data Center-only nature of this feature.

dourget.einhorn what is the problem exactly? You don't have to be a Crowd admin to be group administrator. Have you reported your issue to support?

This feature is buggy in crowd 3.3.2

as a crowd admin  I do not have the possibility to administer group which are delegated to me. 

I agree with all of the comments saying that this feature should be on server. 

We needed to provide browse access to: users, groups and audit log and had to give Full Administrator rights.

Crowd has an incredible low value for dollar comparing to other Atlassian Products.

I have to agree with all of the comments saying that this feature should be on server. 
We are thinking on implementing Crow, but for us there is no reason to go for the data center besides this features. 

A few weeks ago, Atlassian sen an email saying that they are raising the prices because the are offer more features, shouldn't this be included?

Pleas "Don’t #@!% the customer"

I agree with Andreas, Alex, Bill, Yvan, Marek, Illka and all other Atlassian customers in this ticket:

For Airbus Defence and Space it's not acceptable to have this feature only available in Data Center Edition!

Please also provide it for server licenses - asap. We have so many of them running ....

Thanks
Eike

I totally agree with all of that guys! We won't buy a Data Center license just for this single feature!

I have to agree with Yvan. The need for a Data Center license for having such a feature is unjustified. The incentive from Atlassian's side here seems to be purely monetary. I don't see that this is going into the right direction.

I completely agree with Yvan Le Texier. You've made this a Data Center requirement even though it is not the sort of feature that would require Data Center for any other reason. Just to give you understanding, @Marek, there's no way my company's going to buy a Data Center license just for this one feature. Nothing else about Data Center interests us. Maybe check the sunk cost fallacy on this one – y'all developed it, and it's not going to drive sales, so best you just make it available to all Crowd users.

Yup, I'm with Yvan.

This is a very basic feature, which really should have been implemented years ago. I really can't imagine how I would justify the cost of a Data Center license for this one feature, especially since DC only covers one physical location. 

Call me crazy, but in my mind, Data Center is about capacity and resilience,, not about basic product functionality.

Hello Marek

Thank you for this good news but there is still a problem.
We need a Data Center license to use this feature.

When will you listen to your customers ?

The improvement issue raised (CWD-5251) to request this feature on Crowd Server version is ranked by votes :

• #1 out of 65 Improvement or New Feature created since 1st of january 2018
• #1 out of 341 Improvement or New Feature created since 1st of january 2015

It has 35 votes in only 1 month, where this original feature request got 107 votes in 7 (yes seven) years

Don't you think something is wrong about Atlassian's positioning with this new Data Center business target ? Specially on this feature for Crowd ?

What I understand as an Enterprise Customer is that you want to promote DataCenter license which is a subscription over Server license which is a perpetual one.
Your new target is clearly driven by money and not by your customers needs.

Is this aligned with following Atlassian's values for you?

1. Open company, no bullshit
2.  Build with heart& balance
3.  Don’t #@!% the customer

For me it is not.

Hello everyone,

We are pleased to announce that we have released Crowd 3.3 which includes Delegated Group Level Admin in Crowd.

You can download Crowd 3.3 from here: https://www.atlassian.com/software/crowd/download/data-center

Here you can find the release notes: https://confluence.atlassian.com/crowd/crowd-3-3-release-notes-958762272.html

Please note that in order to use Delegated Group Level Admin in Crowd you will need Crowd Data Center license.

You can create your evaluation license for Crowd Data Center here https://my.atlassian.com/license/evaluation

If you need any assistance with the Crowd Data Center installation you can follow our Getting started guide https://confluence.atlassian.com/crowd/installing-crowd-data-center-935369773.html

We hope that you will enjoy this version as much as we do!

Please reply directly to my email to share your feedback or just add your comments in this ticket. We'd love to hear your thoughts!

Best regards,

Marek Radochonski
Senior Product Manager, Crowd
mradochonski@atlassian.com

Count me in on the need for this feature in Crowd server.

Count me in on the need for this feature in Crowd server. This is a gaping hole in the feature set.

This is totally contradictory with Crowd Data Center documentation. where anyone can read the following :

Crowd Data Center is a deployment option specifically designed to support the unique and complex requirements of enterprise organizations, where Crowd is central to the authentication and user management infrastructure. It's currently available for Crowd 3.0, or later. This page provides resources related to Data Center, as well as a high-level introduction to how it works.

To make more money you are trying to diversify versions like in Cloud offers
For hosted version these "more you pay more you get" options are totally ridiculous and we should have only one product.

The fact is that choosing to have high availability is already an infrastructure cost for an enterprise.

And yes as you said in private message Data Center can be setup with one server only.....

But isn't it totally ridiculous that we have to buy a DataCenter license meant for high availability to have it running on a single server ?  just to get delegated group administration ?

DataCenter should stay an optional deployment option. maybe with some optional features but really linked to high availability not like this one.

Even in Microsoft Outlook any distribution list owner can manage his distribution list member....no need to have administrative permission on Exchange Server or any specific license to do this.

By the way anyone interested can vote on CWD-5251 - make group administration feature available to server version

Thank you for your feedback. We appreciate your perspective.

With Atlassian Data Center products we are addressing the challenges enterprise organizations are facing as they grow. You may see similar investments happening in Jira (with archiving and custom fields optimizer) or Confluence (with read-only mode).

Delegated administration in Crowd is targeted at large or growing organizations, thus it has been delivered as part of our Data Center offering.

We are aiming to help these teams as they scale their mission-critical Atlassian applications.

The rule of thumb for Server and Data Center functionalities is that you may expect global admin and infrastructure related features to be part of our Data Center offering.

Also as Data Center features we consider features that:

• provide more control and administration at scale
• deliver uptime and business continuity that enterprises need
• improve performance at scale
• provide deployment flexibility, such as taking advantage of an Infrastructure-as-a-Service provider? (eg. Amazon Web Services or Azure)
• are best built on a multi-node architecture

Even though we use this process across our various product teams, we are constantly challenging ourselves to focus on the needs of each offering’s core customers. Whether you’re using Server or Data Center, we continue to improve our products in a way that reflects your needs.

Your feedback also continues to help us shape the future of Server and Data Center, so keep it coming! While we don’t always get a chance to respond to every request, they do have an impact on our roadmap. We look for feedback in the Atlassian Community, here at our public Jira instance, at Summit, and in all other forums, so we can continue to improve.

Best regards,
Marek | Senior Product Manager, Crowd Server & Data Center

As an heavy Crowd user and intense Atlassian supporter, I would also like to have this feature on Crowd Server. This will make small and medium-sized enterprises work way more smoother than before.

As mentioned by many others in this comment section, this feature will be useful in Crowd server as well.

Please enable this feature also for Crowd Server.

Given Crowd's purpose, being able to admin at a group level just seems like a feature that should be present for all customers.

I do not see any "enterprise only" added value in this feature, this should not be reserved to Data Center license

I couldn't agree more.

I forth Yvan's comment, why is this a Data Center only feature? Especially for smaller organization this is a useful feature so that new user requests do not have to go through the system administrators all the time.

Please enable this feature for Crowd Server.

I echo Yvan and Richard.

I second Yvan's comment - its a bit of a kick in the teeth that something that has been asked for for 7 years is released but only to a subset of customers especially given there doesn't appear to be anything in the change related to the purpose of the Data Centre offering.

Given Crowd's purpose, being able to admin at a group level just seems like a feature that should be present for all customers.

Could you please make this feature available in Crowd Server also and not only for Data center license .

I do not see any "enterprise only" added value in this feature, this should not be reserved to Data Center license

Thank you

Anyone interested can vote on CWD-5251

Awesome to see this feature almost ready 

eike.meinhard87137201 I am glad to hear that this feature might be beneficial to you. We have just released Crowd 3.2 with improvements of the Audit Log and possibility to track all user and group membership changes https://confluence.atlassian.com/crowd/crowd-3-2-release-notes-949250099.html Delegated admin is the next feature that we will be working on and we are aiming to ship it in the next minor release of Crowd. We are currently in an early validation phase of our prototype. If you would like to participate in it then please don't hesitate to get in touch with me.

This feature will dramatically decrease my support tickets regarding group management.

On the European Atlassian Tour you presented this feature as "coming soon". Please provide me a due date or estimation.

Thanks
Eike

Update:

This request, with ninety-eight votes, is seven years old. And the related ticket, CWD-1753, is more than eight years old.

Need this feature. Is there any chance of getting it in this decade?

As a Bitcucket administrator, I would also like to see this added to Bitbucket.

I give Project admin roles to Project leads, but since they can't use groups, they add individual permissions.

Administration would be more manageable if Bitbucket had this feature.

Thank you!!

Rex Core (rcore@ucsc.edu)

+1

It is urgently needed in our Organization.... we have many verticals to manage.... the verticals are asking for this feature from a long time.... please incorporate it asap.

We would like this feature as well... We have to use a centralized helpdesk group to prevent having multiple adhoc admins with rights that could potentially edit ANYONE's group uncontrollably. 

Please implement!

@aragot @rhartono what is the status of this issue?

Hi

Please reconsider adopting this feature, it is crucial for enterprise use.

Best Regards,

Bitbucket Support for CoBa

... but at least in 2.9.1 we got CWD-4475, "Retrieve avatars from LDAP", which had one vote and I'm sure is extremely important.

This request, with sixty-six votes, is five and half years old.

Five and a half. And the related ticket, CWD-1753, is almost seven years old.

For an enterprise product.

This is a major feature in an enterprise environment. Please consider to implement a solution for this.

I agree with @adaly that this is a crutial feature and I'm still amazed that it has not been implemented in over 4 years.
Delegating the user management to nominated and trusted but non-admin users is a must-have ! We atlassian customers can adapt to the way you implement it, but we need at least one way to do this...

The ability to delegate user/group management while restricting system management functions is just basic security hygiene for any application. I am quite amazed that this product STILL doesn't offer this function.

Please consider that:

1. Enterprise buyers are expecting to see the common elements of IT security architecture in applications they buy, such as separation of duties and administrative delegation

2. All buyers prefer applications where system settings are protected from change by inexperienced or malicious users, and prefer not to grant all possible rights when only a subset are needed

Therefore, regardless of any other features you decide to offer in this area, please start with the separation of system administration from user administration.

BTW, as of today, this is the 3rd most voted feature, not counting the ones that have been explicitly dropped from the Crowd roadmap but are still open.

Can we gent an update on this issue? It would be good to know if it is anywhere in future Crowd improvements or if it will be abandoned/ignored

Hi there,

for my customer the missing of this feature might be a reason not to use crowd.

We need a scenario where the administrator setup the groups of the project but leave the administration (incl. group membership care taking) to the specific group admin. Because of security reasons those admins are not allowed to administrate other projects, too.

Would be interessting to know if this feature has been scheduled yet.

Greetings from Germany

Stefan

This will also help us a lot!

Hello, is there any movement on this issue? I would love to see this implemented.

Needing something I created a few php scripts that might do this for some others, you can find them at:

https://opensource.ncsa.illinois.edu/stash/users/kooper/repos/crowd-group/browse

You will need to create your config.php that has a application account and password to connect to CROWD. I have this installed on the same server that we run crowd on in apache. Crowd runs behind apache in it's own tomcat container hence the 127.0.0.1 for IPaddress when configuring the SSO token.

This was a short code project so pretty it ain't, but it fulfilled my/our needs.

We have an instance that supports many different opensource projects. The system has support for jira, confluence, stash, fisheye, bamboo, nexus and jenkins. We use the groups feature of crowd to control access to spaces, jira issue assignment, write access to stash, etc. Right now when a new user wants to start development they can create their own account but have to contact the crowd administrator to add them to group. This feature would allow me to appoint a person of an opensource project to decide who is a member.