
Documentation for Crowd 2.0.x. Documentation for other versions of Crowd is available too.
This page introduces you to groups and roles in Crowd.
Groups and roles are known as permission container objects. Groups are particularly important in Crowd, as they are often used to control access to applications. Note also that the crowd-administrators group confers Crowd administration rights to its members. Roles are used less frequently, depending on the requirements of individual applications.
Crowd's role-based access control could be enhanced
At present, the implementation of roles in Crowd is identical to the implementation of groups. Additional development work would be needed to differentiate the functionality of roles from groups. If you would like to help us to design better role-based access control, please add a comment to the improvement request CWD-931, letting us know how you would like to see it work.
About nested groups
Some user directories allow you to define a group as a member of another group. Groups in such a structure are called 'nested groups'. In Crowd, you can map any group to an application, including a group which contains other groups. Crowd supports nested groups for LDAP directory connectors, Crowd internal directories, Delegated Authentication directories and custom directories. You can enable or disable support for nested groups on each directory individually. For more information, refer to the documentation on configuring a directory.
For more details about nested groups, refer to Nested Groups in Crowd.The Group Browser and the Role Browser are very similar. They allow you to search, view, add and edit the various groups and roles stored within a specified directory.
To use the Group Browser,
Screenshot 1: Group Browser
Screenshot 2: Viewing and updating group details