Documentation for Crowd 2.9. Documentation for earlier versions of Crowd is available too.

Skip to end of metadata
Go to start of metadata

In Crowd, users are referred to as user entity objects or just users.You can either import users into Crowd in bulk (see Importing Users and Groups into a Directory), or add them individually as described below.

To add a user:

  1. Log in to the Crowd Administration Console.
  2. Click the Users tab in the top navigation bar.
  3. Click Add User in the left-hand menu.
  4. Complete the following fields:
    • Email — The email address of the user. Email addresses must follow the RFC2822 format.
    • Active — Only deselect this if you wish to deny the user access to the Crowd-integrated applications.
    • Username — The user's login name. Within a given directory, the username must be unique. Note that you cannot change the username once the user has been created.
    • Password — The user's password.
    • Confirm Password — Enter the same password again, to ensure that you have typed it correctly.
    • First Name — The user's first name.
    • Last Name — The user's last name.
    • Directory — The directory to which the user will be added. Note that the user cannot be moved to a different directory once the user has been created.
  5. Click Create to add the user.

After creating the user, you will be able to specify the user's attributes and group membership. If you wish, you can also verify that the user can log in to appropriate applications.

Automatically adding users to JIRA or other groups

You can configure your directory to automatically add users to one or more groups. Define the default groups on the directory as described in Automatically Assigning New Users to Groups. For example, you can add JIRA groups as default groups for your LDAP directory connector. Whenever a new user is added to LDAP, they will automatically get access to JIRA.


Crowd Documentation


  1. Password doesn't make sense with a Delegated Auth directory,  does it?   Can we get some more explanation about this

    Edit – I answered my own question:

    • in rare instances when you add the person to the group from the application (jira, stash, whatever),  it will create a user within crowd which can then be assigned groups.   I find this difficult to replicate.
    • a person can just log into the app,  then crowd will create them if the app cannot find the user in another directory
    • if you have a small number of legacy users to migrate,  you can use the add user dialogue for a single user,  and enter fake password for the password field.  This will not harm the users login because it is delegated to the LDAP directory anyways.

    For migrating users to crowd you can easily test which directory the app is getting them from by the user search dialog.   It will say Crowd when it is getting them from crowd,  and the groups should be readonly within the app.

    For Stash,  I ended up scraping a small list of users off the stash group listing,  and pasting them into the example CSVs provided for crowd user and group import,  editing them in notepad++.   Not too bad.   Omitted the password field,  since this is a delegated Auth.  It imported just fine.   In Stash,  I saw the Crowd directory find the users first,  so they became crowd users just like that.

  2. Unfortunately the following is still wrong...

    "If you have configured an email server and a notification template, Crowd will send the user an email notification about their new password."

    As per CWD-1320 - Getting issue details... STATUS and several others - this functionality is still not available.

    Please correct the documentation at least - thanks!


  3. is there a way of sending out automatic emails to new users?