Grouper types helps support and clarify the usage of types as defined in the TIER the Grouper Deployment Guide.
This is a more structured and consistent way of accomplishing what could also done through the attribute framework.
If the type is "service", and it is an indirect assignment, and the folder which assigns it has a display extension of "Student systems", then followup with a sentence (note, the folder should be linkable to that folder): This is the Student systems service.
|ref||group/folder||Reference groups are institutionally meaningful cohorts used in access policy.|
|basis||group/folder||Basis groups represent arcane codes or attributes from external systems are used generally in reference groups and not directly in access policy.|
|readonly||group/folder||Read-only groups should not have membership changes except by the process that manages the group; perhaps external from the central authorization system|
|policy||group/folder||Access policy groups are used by downstream systems to allow or deny users access to services or resources.|
|bundle||group/folder||Bundles are reference groups which aggregate multiple other reference groups. Reference groups are institutionally meaningful cohorts used in access policy.|
|security||group/folder||Security groups are collections of entities who have from access privilege on a group/folder/attribute, e.g. studentSystemAdmins.|
|org||group/folder||"Org" or organization groups or folders are delegated to and owned by organizations in the community.|
|test||group/folder||Test groups or folders are not used in production systems. They could be for dev, test, performance, etc environments.|
|app||group/folder||App groups or folders exist to be used in a specific application.|
|service||group/folder||A service is a collection of one or many apps that comprise of a service offered to users.|
Use the "More actions" button to access Type.