|
|
| Line 126: |
Line 126: |
| <!--T:32--> | | <!--T:32--> |
| Click on [https://ccdb.computecanada.ca/me/facilities Local Accounts] and it will give you a list of the consortia with links to click on to get an account at that consortium. Note that consortium or local accounts are needed only to log in to our legacy systems. Users can log in to any of the new national systems with their Compute Canada credentials. | | Click on [https://ccdb.computecanada.ca/me/facilities Local Accounts] and it will give you a list of the consortia with links to click on to get an account at that consortium. Note that consortium or local accounts are needed only to log in to our legacy systems. Users can log in to any of the new national systems with their Compute Canada credentials. |
|
| |
| = How to manage RAP memberships = <!--T:38-->
| |
|
| |
| <!--T:41-->
| |
| A PI can manage RAC RAP memberships at any time on CCDB.
| |
|
| |
| <!--T:42-->
| |
| Any user with an active Compute Canada account can be added as a member to a RAP.
| |
|
| |
| <!--T:43-->
| |
| But the PI can change this. The PI may want to allow access to user roles they are not sponsoring (i.e. a co-PI). A PI may also want to remove one or more of their sponsored user roles from their RAC RAP and limit them to only be able to access their default RAP.
| |
|
| |
| <!--T:39-->
| |
| 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.
| |
| *Manager: Members of a RAP can be promoted to Managers by the Owner of the RAP or by another Manager. Managers can also be demoted to Members by the Owner of the RAP or by another Manager. By default, Managers also have the permissions of RAP Members.
| |
| * Member: Members can use the PI’s allocation in the corresponding Compute Canada system(s). Members cannot make any modifications to the RAP memberships.
| |
|
| |
| <!--T:40-->
| |
| RAP membership is represented as a group in LDAP. It defines a group of users that are authorized to submit jobs against the RAPI (which is the Id of the RAP) and share files within the same Unix group.
| |
|
| |
|
| = Further Help = <!--T:33--> | | = Further Help = <!--T:33--> |