Restrict Visibility of Custom Fields by Staff Role/Permission
Currently, any staff member with access to view a profile can see all fields on that profile, including custom fields. This creates a challenge for foundations that want to store sensitive information, such as wealth screening data or estimated net worth in CSuite, but only want certain staff members to have visibility into those fields.
We would like the ability to:
- Mark a custom field as restricted or private.
- Control which staff roles or individual users can view that field.
- Hide the field entirely from users who do not have the appropriate permission, rather than simply displaying a blank value.
This would allow foundations to consolidate sensitive donor data within CSuite rather than maintaining it in separate, disconnected tools, improving data integrity while respecting internal access controls.
1
vote
Mark Bejcek
shared this idea