What is the purpose of Crowd???

Is there any purpose to Crowd apposed to the Jira User management system? What does Crowd offer that the Jira user management can't do?

Does anyone know?

4 answers

Only with Crowd you get SingleSignOn

0 votes
Tarun Sapra Community Champion Mar 06, 2014

Hi Warren,

Crowd serves a very important purpose if you intend to use other atlassian products with jira like stash/bamboo/confluence. It provide Signle-Sign on and can handle application/directory mapping really well, for large installation of atlassian products you can't rely on JIRA user mgmt. Also If you wan to buy different user license for different atlassian products like 25 user for stash/ 50 for confluence and 100 for jira in that scenario all accumulated users can use Crowd and things are in much better order, I can't imagine doing something like that with JIRA user management.

Hope it helps.


Crowd is useful for larger organizations - multiple LDAPs spanning many users. Also if you have custom auth that isn't a typical LDAP.

It provides caching - something JIRA doesn't do as well.

It can also help you get around firewalls and other security policies in the organization.

Hi Warren,

I will try to explain you what is Crowd in the light of your other questions as well. From the start, I'm a developer, not on Atl team, but I hope I will put it in plain English.

So: Crowd is a Atlassian custom user management system. Its purpose is to provide a common auth mechanism for all Atl products (architecturally speaking: component reusing). If you install only JIRA, there's always a Crowd instance embedded into JIRA responsible for auth and user management.This local instance can delegate calls to an external instance as well, and this is how Crowd servers are used to create the SSO mechanism.

This change was introduced, if I remember well, in 4.x versions


  1. Atl products are well integrated
  2. You configure one product once, you know what to do with the rest. Plus, the config is much simplified (my opinion).


  1. Support for standard SSO out-of-the-box is missing (no SAML, Kerberos, ... although there are plugins to do that)
  2. User data is pretty much caught in the Atl paradigm (mail, username, fName, lName)


You are asking those questions because you want to pass over some limitations of Crowd. Thankfully all Atl products are extensible, so to resolve the problem of having multiple emails in JIRA you can add - for instance - custom attributes on the user and notify not only the main address but the address taken from properties as well.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,711 views 17 21
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you