Crowd User's Glossary
Here is a list of all entries in the glossary, plus the first few lines of content. Click a link to see the full text for each entry.
Crowd allows you to have different usernames in different applications. These different usernames are called 'aliases'. Your Crowd administrator can manage your aliases for the applications you are authorized to access.
If you are authorized to use Crowd, you can log in to Crowd's Self-Service Console to update your user profile and view other information about your username. The Crowd administrator can grant people access to the Self-Service Console, as described in the Crowd Administration Guide. Basically, the administrator should ensure that your username is in a user directory which is mapped to the Crowd application.
A Crowd administrator is a user who has access to the Crowd Administration Console, which provides the functions described in the Crowd Administration Guide. The first administrator is defined during the installation of Crowd. A Crowd administrator can grant administration rights to other users, as described in the Crowd Administration Guide.
A 'Crowd-connected application' is a software application which has been designed and configured to use Crowd for user logins. These applications pass all login requests to Crowd for authentication. Depending on the integration level, the application may also make use of the groups and roles defined in Crowd for authorization purposes, and allow single sign-on across the Crowd domain. The Crowd Administration Guide tells you how to connect an application to Crowd.
Crowd uses the term 'directory', or 'user directory', to refer to a store of information about a user. Typically, a directory will hold your username, name, password, email address, and so on. Your Crowd administrator can define one or more directories internally in Crowd or connect one or more external directories to Crowd.
A group is a collection of users. Administrators create groups so that the administrator can assign permissions to a number of people at once. For example, it is quicker to give group 'X' access to JIRA, rather than giving every team member access individually. In Crowd, each group belongs to a specific directory. It is possible to have two groups with the same name, such as 'X', in two different directories. A user can be a member of group 'X' in one directory, in both directories or in neither
Support for roles, previously deprecated, was removed in Crowd 2.5.
Authorized Crowd users can access the Crowd Console, even if they are not Crowd administrators. Non-administrators will see a subset of the Crowd Console functionality, which we call the 'Self-Service Console'. The Crowd User Guide describes this functionality. The Crowd Administration Console presents the full range of Crowd administration functionality to authorized Crowd administrators.
Single sign-on (SSO) is a feature offered by Crowd. Your Crowd administrator can choose to enable this feature for the Crowd-connected applications. If SSO is enabled, you will only need to log in or log out once.
Was this helpful?
Thanks for your feedback!