cc_staff
3
edits
(Marked this version for translation) |
No edit summary |
||
Line 106: | Line 106: | ||
= How to manage RAP memberships = <!--T:38--> | = How to manage RAP memberships = <!--T:38--> | ||
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. However, a PI can at any time deactivate any role they sponsor. | |||
Membership in any of a PI's RAC RAs can be modified. By default when a new RAC RAP is created for a PI, all of their sponsored user roles will be originally set up as members of this RAP. | |||
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--> | <!--T:39--> | ||
A PI can manage RAC RAP memberships at any time on CCDB by adding or removing user roles from their RAP. There are three RAP membership permission levels:and | |||
*Owner: | *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: the | *Manager: the Owner or any manager of a RAP can give manager permissions for that RAP to any of its members. Similarly, they can remove manager permissions from any member. | ||
*Member: the | *Member: the Owner or any Manager of a RAP can add any CCDB role as a member of a RAC project. Similarly, they can remove the membership of any role. | ||
<!--T:40--> | <!--T:40--> |