Contact Card Manager and clones of it inherently give access to see user fields regardless of Profile Publish Access settings for Non-Teaching Staff. Schools would like a way to still manage visibility of specific fields to Contact Card Manager in nuanced situations.
Upon further exploration and conversation, the Directories did fill the need. I think this is part of the terrifically confusing nature of roles and figuring out what they do in the system. The update to the roles list is definitely helpful; I hope further work is going to be done to help improve and clarify the roles and associated tasks and reports.
The goal of the Contact Card Manager role was to give full DBA access to contact cards and all its information without having to clone the Platform Manager (and inherit some of those hidden tasks). Can you tell me more about who you are giving this role to? Why this role instead of another? When trying to grant access to contact cards for students and parents, is there a reason that Directories don't fit the need? Thanks for helping me understand the need here!
good idea!!
We need to be able to grant PeopleFinder access to staff for students and parents, but not allow them access to employee personal contact information.