cc_staff
158
edits
Line 75: | Line 75: | ||
<b>Default RAP: </b> All of a PI's activated sponsored user roles are always members of the PI's default RAP. That is, confirming sponsorship of a user, confers on them membership in a PI's default RAP. This cannot be modified. However, a PI can at any time deactivate any role they sponsor. | <b>Default RAP: </b> All of a PI's activated sponsored user roles are always members of the PI's default RAP. That is, confirming sponsorship of a user, confers on them membership in a PI's default RAP. This cannot be modified. However, a PI can at any time deactivate any role they sponsor. | ||
<b>RAC RAP:</b> Membership works differently depending | <b>RAC RAP:</b> Membership works differently depending on whether the RAC RAP has HPC or Cloud resources allocated: | ||
*HPC resources: When a new RAC RAP with HPC resources (e.g. CPU, GPU, project storage, nearline storage, etc.) is created for a PI, all of their sponsored user roles are automatically set up as members of this RAP.
| *HPC resources: When a new RAC RAP with HPC resources (e.g. CPU, GPU, project storage, nearline storage, etc.) is created for a PI, all of their sponsored user roles are automatically set up as members of this RAP.
| ||
*Cloud resources: When a new RAC RAP with Cloud resources allocated is created for a PI, only the PI is added as a member of that RAP.
| *Cloud resources: When a new RAC RAP with Cloud resources allocated is created for a PI, only the PI is added as a member of that RAP.
|