User Profile: Contact Card (tab)
View and update information about the various ways to contact a user or who to contact on the user's behalf (such as in an emergency). Manage general information about the user to develop strong relationships.
You can view, query, and report on this data, and data managers can update the information via a data import. Data managers can also update "admin view only" fields with a data import.
-
Select Core.
-
Select People finder.
-
In the Type a name field, enter and select the name of the individual you want to work with. The selected individual's profile page appears.
-
Select Contact card.
If specific data hasn't been saved to the individual's profile record, the corresponding field may not appear on the contact card.
Additionally, some fields may be hidden from your view even though the data is saved to the user's profile.
-
Platform managers determine which information users with your security role can view about others via profile publish access settings.
-
Each individual can further limit what users with various security roles can view via their account profile privacy settings.
Platform managers and contact card managers should regularly acknowledge data changes made to user profiles. For instructions, see handle profile changes.
Most employees who are responsible for keeping user profile data updated should have the contact card manager role instead of platform manager role (and its clones).
Tip: Learn how to manage roles and tasks for users.
Contact card managers can handle personal data common to any user (including contact information, demographics, relationships, emergency contacts, business, and education information).
-
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 the contact card manager 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.
We recommend schools grant the platform manager role sparingly.
Schools should avoid granting users a clone of the platform manager role, even when they remove unwanted tasks to limit the clone's access (as much as possible) to only contact card functionality. If your school relies on clones, consider replacing them with the contact card manager role instead.
When platform managers receive new tasks or an existing task it updated, schools with clones must review the clones to ensure their access is still appropriated limited (not too little nor too much power).
Some school may have user profiles with content attachments and links that were originally stored in Podium profiles. If a user records includes this content, an Attachments tile appears on the Contact card of the user’s Core profile. You can find use the People finder to access the Contact card tab for a user whose record includes this sort of legacy content.
Although you can’t add new attachments from here, you can select a file from the tile to view and download an existing legacy attachment. Users can’t view attachments about themselves.
For schools that want to retain this content permanently, we strongly recommend you download the files. Then from Core, select System tools, Bulk upload, Manage user files and re-upload the content so that it appears in the user’s Files and Forms instead. After you save the desired content, Delete the legacy attachments from the tile on the user’s Contact card.