VO Membership Information
Expressing VO group membership and role information
This page contains information about using Check-in for managing your Virtual Organisation (VO). For joining a VO please look at Joining Virtual Organisation.
In simple terms a Virtual Organisation (VO) is just a group of users. In EGI VOs are created to group researchers who aim to share resources across the EGI Federation to achieve a common goal as part of a scientific collaboration. For a more formal definition of VO please look at the EGI Glossary.
You can browse existing VOs in the EGI Operations Portal. For each VO you can click on the Details link to get more information. You can join an existing VO either using the enrollment URL or emailing VO managers.
If you are interested in creating your own VO, please see instructions in the section below.
VOs in Check-in are represented as groups that go beyond simple collections of users, providing structured membership management and advanced enrollment workflows tailored for complex access needs. VOs can also be organised in a hierarchical structure for creating groups or subgroups within a VO.
Any person who can authenticate to the Operations Portal using their EGI Check-in account can register a new VO.
The person initiating the registration is called the VO manager. After the VO is set up and operational, the VO manager is the person who is primarily responsible for the operation of the VO and for providing sufficient information about VO activities for EGI and for VO members (to both people and sites).
A step-by-step guide for the VO registration process is provided in the procedure PROC14 VO Registration.
Groups are managed by Group Admins, who have several key responsibilities:
Note: Group Admin is not a role within the Group; it is a separate administrative designation. Group Admins have the ability to manage all aspects of the Group, as well as any sub-groups in the hierarchy, including roles, memberships, and configurations.
Members of Groups are assigned roles upon joining. Users can join a Group in one of two ways:
Each assigned role includes an entitlement attribute, which grants authorization to specific resources. This flexible approach to role assignment allows Group administrators to control access while offering users the ability to select roles when available.
Note: Entitlement values can be found on the Group Details Tab
Members of a Group can have different statuses that affect their access and entitlements:
Active: The membership is fully active, and the user receives all entitlements associated with the roles they hold in the Group.
Suspended: Administrators can suspend a user’s membership for security reasons, such as suspicious activity. While suspended, the user retains membership but loses all entitlements tied to their roles. Administrators can later revoke the suspension and reactivate the membership.
Pending: A user’s membership can have a future start date based on the enrollment configuration used during joining. This scheduled membership will activate automatically on the specified start date. Administrators also have the option to activate the membership manually if needed.
Note: Suspension/Activation of a member will also affect all memberships in Sub Groups of target group
Each status provides Group administrators with flexible control over user access and helps ensure security within the Group.
Memberships in Groups come with a defined duration, which may be set to indefinite if allowed by the Group’s configuration settings. However, the duration of any membership is also affected by the Group’s position within the Group hierarchy. Membership in a higher-level Group imposes a duration limit on all memberships in its subordinate Groups. As a result, the expiration date for any membership in a lower-level Group cannot exceed the duration limit set by the higher-level Group.
When viewing members within a Group, you will encounter two types of expiration dates:
For example, if a user’s Direct Membership Expiration in a lower-level Group is set to indefinite (or a date beyond 2024), but the Effective Membership Expiration from a higher-level Group is November 12, 2024, the user’s membership will expire on November 12, 2024, in line with the higher Group’s restrictions.
This hierarchical approach to managing memberships allows for simplified administration and ensures consistent access policies are maintained across different Group levels.
Some enrollment flows or invitations may specify a starting date in the future. In these cases, users who accept the invitation or submit an enrollment request will have a pending membership status until the specified start date. Once the start date arrives, the membership will automatically activate, changing their status from pending to active.
The Group Details Tab provides essential information and management options, including:
To add a new role, enter the role name in the text input field and click the
plus button to create it.
Note: A role cannot be deleted from a group if it is assigned to any members.
Locate the role you want to remove and use the minus button next to it to delete
it.
There are two ways to create a subgroup within the platform:
Note: Top-level Groups and Sub-Groups that contain additional Sub-Groups cannot be deleted.
Users can be added to a group either by invitation or direct addition:
Sending an Invitation to a User or directly adding them the group can be achieved by:
NOTE: Once a user accepts or reject an invitation email notification will be sent to admins of the group
Users can be added to a group by creating an Enrollment Request. Enrollment Requests can be created through the Enrollment Discovery Page or a Direct Enrollment Link. The Enrollment Discovery has available all the visible and active enrollment flows and the Direct Enrollment Link points to a single Enrollment Flow that must be active.
Α) Sharing the Enrollment Discovery Page Link following these steps:
NOTE: Once a user submits an enrollment request admins of the group will receive an email notification.
B) Sharing an Direct Enrollment Link to a specific Enrollment
NOTE: Once a user submits an enrollment request admins of the group will receive an email notification.
NOTE: Removing a member from a group will also remove them from all Sub Groups.
NOTE: Once a group member is removed admins of the group and the removed user will receive an email notification
User memberships can be suspended or activated by a group admin by following these steps:
NOTE: Once a group member is activated/suspended, admins of the group
and the user will receive an email notification.
NOTE: Selecting a user discovered in the select input and will add the user immediately. Once a User accepts or rejects an invitation and when a user is added directly to a group, group admins receive email notification
NOTE: Once a group admin is removed from a group he and all other admins are sent an email notification
User enrols to a group using a specific enrollment, each enrollment has a configuration that defines the following things:
Enrollment Name: The identifying name of the enrollment.
Membership Expiration: The duration of the memberships of users enrolled with this enrollment. See more
Start Date: Allows for memberships to be activated in future time and not directly after an enrollment is completed.
Requires Approval: When enabled, enrollment requests submitted by users need to be approved by an administrator; otherwise, requests will be automatically approved.
Comments: If activated Users that are submitting an enrollment request need to also provide additional information.
Acceptable Use Policy (AUP): Acceptable Use Policy in the form of a URL.
Available Roles: Available roles to users using this enrollment.
Multiselect Roles: If activated users using this enrollment can select multiple roles.
Visible to non-members: If activated the enrollment will be available in the Group Enrollment Discovery Page.
Is Active: Only active enrollments can be used for user enrollments.
Each group has a group enrollment discovery page where users can view all the available (visible) enrollment flows. Selecting an enrollment flow and using the submit button after filling the form creates an enrollment request. Enrollment requests can be used to create a new membership to a group or update an existing one. Always preselected is the default enrollment flow.
The Enrollment Discovery Page is accessed through a URL using the group path of a group following this format:
https://aai.egi.eu/auth/realms/id/account/#/enroll?groupPath=/group/path/example
NOTE: When updating an enrollment configuration, all ‘pending approval’ and ‘Waiting for reply’ enrollment requests with this configuration are archived.
NOTE: When deleting an enrollment configuration, all ‘pending approval’ and ‘Waiting for reply’ enrollment requests with this configuration are archived.
All enrollment requests—no matter for the status—are accessible through the Account Console for Group admins. When a user submits an enrollment request to join a Group and the request requires approval, Group admins are notified via email. These notifications include a direct link to the request that needs to be reviewed, streamlining the approval process. Admins can view and manage these enrollment requests directly from their Account Console, making it easy to keep track of pending requests and process approvals in a timely manner.
To review an enrollment request follow these steps:
NOTE: After approving or denying an enrollment request email notifications are sent to the requesting user and other administrators of the group
Information Available when reviewing an enrollment request:
Submission Date: Date and time of the submission of the request by the user.
Enrollment Request State: State of the request. (Pending Approval, Approved, Rejected, Self Reviewed, Archived)
The User Details at the time the enrollment request was created:
Full Name: Full name of the user when the request was submitted.
Email: Email address of the user when the request was submitted.
Authentication Providers: Authentication provider(s) used by the user for submitting the request.
Assurance: Information for assessing the confidence level in the identity of the user when the request was submitted.
Full Name: Current full name in the user profile
Email: Current email address in the user profile
Linked Identity Providers: Authentication providers linked to the user’s profile.
Group Name: Name of the group
Enrollment Name: Name of the enrollment configuration used
Group Roles: List of the roles that the user will acquire from this enrollment request
Acceptable User Policy (AUP): Link of the AUP that the user has approved
Membership Expiration Days: The duration of the membership in days. See more
Comments (or custom name): Additional information from the user submitting the request.
Expressing VO group membership and role information
VO management through the EGI Attribute Management service Perun
X.509 / VOMS based authentication and authorisation