rsnt_translations
56,430
edits
No edit summary |
No edit summary |
||
Line 84: | Line 84: | ||
There are three RAP membership permission levels: | There are three RAP membership permission levels: | ||
*Owner: The PI is the sole owner of the RAP and all the allocations associated to that RAP. This cannot be changed. The owner can add or remove RAP managers and members. | *Owner: The PI is the sole owner of the RAP and all the allocations associated to that RAP. This cannot be changed. The owner can add or remove RAP managers and members. | ||
*Manager: An elevated permission (on CCDB only, not on the clusters) delegated by the owner or another manager that allows making membership changes. Managers can also use the PI's allocation in the corresponding cluster(s). Important: Members that have promoted to <i>Manager</i> on a RAC RAP cannot make changes (e.g., change ownership of the files, apply ACLs, manage permissions on Globus, etc.) on the project/nearline file systems on behalf of the PIs. | *Manager: An elevated permission (on CCDB only, not on the clusters) delegated by the owner or another manager that allows making membership changes. Managers can also use the PI's allocation in the corresponding cluster(s). Important: Members that have been promoted to <i>Manager</i> on a RAC RAP cannot make changes (e.g., change ownership of the files, apply ACLs, manage permissions on Globus, etc.) on the project/nearline file systems on behalf of the PIs. | ||
* Member: Members can use the PI’s allocation in the corresponding cluster(s). Members cannot make any modifications to the RAP membership. | * Member: Members can use the PI’s allocation in the corresponding cluster(s). Members cannot make any modifications to the RAP membership. | ||