Platform managers can clone a role to assign it to a user, but not all the tasks associated with the role. In order to clone the appropriate role, the Platform Manager must understand the role's tasks and permissions.
Warning: Due to the intricacies of certain manager roles (ex: Platform manager, Page manager, Pushpage (Newsletter) manager, etc.), cloning these roles may not produce the desired effect as the cloned role may have more access than desired. We recommend testing the cloned role before assigning membership to ensure that security issues are not introduced.
Warning: When new features are released or existing features are updated, the original role might receive new tasks or an existing task may have updated functionality (such as a new button on an existing screen). You may need to review the clones to enable a new task or disable existing tasks based on those updates to be sure the clone doesn't have too much or too little power.
From Core, select Security and then select Roles.
Enter a Role name for the new role.
Select an existing role and select Next.
Select the navigation tasks to associate with the new role and select Next.
To add members to the role, search for each user by selecting any combination of the following criteria in the "Enter Search Criteria" box:
Role: Select from any of the Active roles listed.
Grad year: Choose a specific Grad year or search using All.
Search in: Choose from Last name, First name, Email, Maiden name, Business name, User ID, Host ID.
Select the right arrows (>>) to add the users.
Select Save & exit.
Although users with the Platform manager role (and its clones) can handle profile changes, we recommend schools grant the platform manager role sparingly.
Warning: Previously, many schools cloned the platform manager role and then manually removed tasks to limit the clone's access (as much as possible) to only contact card functionality. However, when platform managers received new tasks or an existing task was updated, schools had to review the clones to ensure their access was still appropriated limited (not too little power, not too much power). If your school uses clones in this way, consider replacing these clones with the contact card manager role instead.
Instead, most employees who are responsible for keeping user profile data up to date should have the Contact card manager role instead. If you have this role, you can manage personal data common to any user (including contact information, demographics, relationships, emergency contacts, business, and education information).
With this role:
From Core, you can use the People finder to go to a user's profile and Contact card to make changes.
From Core, Users, you can also select Handle profile changes to review the changes users have made or that other administrators made on a user’s behalf.
We recommend schools also use this role to grant API access to any of our third party partners who rely on accessing or updating Contact card data. It ensures that the API access is limited strictly to the data they need.
Tip: Review how to manage roles and tasks for users.
Tip: To limit directory results by school level, campus location (for a school with multiple campuses), or other groupings, we recommend you create a clone of the "friend" role for each desired grouping. Then add users to the appropriate role. Finally, create a new directory or edit an existing one to use the new roles.