rsnt_translations
56,430
edits
No edit summary |
(Marked this version for translation) |
||
Line 107: | Line 107: | ||
= How to manage RAP memberships = <!--T:38--> | = How to manage RAP memberships = <!--T:38--> | ||
<!--T:41--> | |||
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. | 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. | ||
<!--T:42--> | |||
Membership in any of a PI's RAC RAPs 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. | Membership in any of a PI's RAC RAPs 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. | ||
<!--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. | 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. | ||