Give Directory Access based on matching permissions
K
Kelly Gendron
We learned today that if someone has multiple constituent types (i.e., Alumni and Parent) they will be blocked from the Alumni Directory search if we have not given PARENT access. I think that if one of the types matches the permissions that are not restricted, they should be allowed access.
Sahil Mallick
Hello Kelly Gendron! I have a few more questions for you:
- Can you provide examples of scenarios where a user might have multiple constituent types and how you would expect the access to be handled?
- Are there any specific constituent types that should always have access regardless of other types they might have?
- How critical is this access issue to your operations, and what impact does it have on your users?
K
Kelly Gendron
Sahil Mallick hello. We have several alumni who are also faculty/staff members at our school. I am sure this is common at most of your partner schools. We also have many who are alumni and a parent. However, since we had only wanted to give access to the directory to alumni at this time, we restricted access to all constituent codes except for alumnus/a and alumni. However, when our constituents with multiple types added all of their types, they were not able to access the directory/search after signing up. If someone is an alumni, regardless of other types that might fit their constituency, it should allow them access, rather than restricting them because they are matched to a restricted value. Currently, having to remove "parent, parent-former, faculty, staff, faculty/staff" it is leaving the door open for more non-alumni to try to get onto the directory at this time.