Similar to Grouper Hooks, but instead of Java logic, built in actions or expression language scripts can be executed
If your Identity Management System does not support external users (e.g. via EPPN), then Grouper can manage that with self registration and or invitations which will can provision memberships
A group in one Grouper can be sync'ed with a group in another Grouper. For instance if two institutions want to share a group of subjects but store them in their own Grouper
User interface to define, view, and assign attributes and permissions in Grouper. The attributes can be assigned to many types of Grouper objects including Groups, Folders, Members, Memberships, etc. The permissions are used as a central permissions management system for other applications at your institution
If you cannot connect Atlassian applications (e.g Jira, Confluence) to your Grouper managed LDAP, then you can use this connector which used Grouper Web Services to manage your Atlassian groups and person information
A permission assignment can be an allow or disallow (to filter out allows inherited from another assignment)
A run-time decision can be applied to immediate permission allows so that context environment variables can change an allow to a disallow. e.g. permissions are only allowed at a certain time of day or from a certain IP address. Grouper can calculate this on the server or the client can get the limits and calculate them.
Grouper 2.0 web servers will accept clients coded against the 1.6 or previous WS API's
This allows you to query the state of Grouper at a point in time in the past or a date range in the past. You can query for memberships, privileges and permissions.