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

Skip to end of metadata
Go to start of metadata

This tip applies if you:

  • Have public-facing JIRA, Confluence and Bamboo servers and private LDAP repositories.
  • Allow public signup via JIRA, Confluence and/or Bamboo.
  • Want to partition where users are created via the public signup functionality.

Crowd allows for multiple directories to be assigned to an application. Follow these steps to direct all public signups into your chosen Crowd directory:

  1. Define two directories in Crowd:
    1. An internal directory for 'public' users.
    2. An LDAP directory for staff and contractors.
  2. Assign both these directories to the 'JIRA' application in Crowd. (See Mapping a Directory to an Application.)
  3. Use the 'ordering' arrows to move the internal 'public' directory into the first position. (See Specifying the Directory Order for an Application.)
  4. Grant the 'Add User' permission to the 'JIRA' application in the internal 'public' directory. (See Specifying an Application's Directory Permissions.)
  5. Ensure that the 'Add User' permission is disabled for the 'JIRA' application in the private LDAP directory.

Using this configuration, when Crowd receives a request from JIRA to create a user, Crowd will create the user in the 'public' internal directory only.

Unless otherwise instructed, Crowd will add the user to all directories assigned to the 'JIRA' application. The above steps allow you to ensure that the signed-up users are added to your 'public' directory only.


  1. Is the public sign up applicable for stash as well? We have integrated stash with crowd and were interested in enabling public signup. Please advice.

  2. Is this really working with the newest versions, because my new user (created in JIRA via public sign up) is every time created in the internal directory of JIRA - even if it's deactivated.