Make contact card field access consistent across personas (adhere to profile publish access)

Apologies if this was already posted, and I missed it. We recently ran into an issue where a particular employee (Learning Support team) noticed they couldn't see DOB when accessing a student's contact card in the Academics persona, but that they could see it if they pulled up the student from the Faculty persona. We were told the profile publish access really only affects the Faculty/Parent/Student personas for directory/roster view, and that the Core/Academics/Enrollment Management areas were more tied to managerial roles. But we can't really control those managerial roles, and for DOB, in this case, we'd have to give them access to all fields, essentially, including edit access, which they do not currently have, of course.


While I agree certain roles should have total access (Platform Manager, Contact Card Manager - though I wish we could even parse that out a bit into smaller roles of access), without the chance to manipulate what other managerial roles have access to, it's an all or nothing component, and people shouldn't have to be asked to remember that a field is available in one place, but not another. If we could manage contact card info access just be setting it at the profile publish access level, and have that apply across contact cards in the system, that would be preferred and more transparent. Thank you!

  • Zach Limoges
  • Feb 26 2024
  • Attach files