Constituent Merge Process should be site secured
The Constituent merge processes that are set up are not site secured. This would be consistent with other processes that are set up throughout the system and would be helpful in a federated agency.
Jun 29 2015
Organization Name (Please enter full organization name)
Enter a subject
Log in / Sign up
Identify yourself with your email address
You won't be notified about changes to this idea.
No site security on R68 process and reports
Site Security applied to Constituent Documentation area.
The additional of Site Security to the Geo-Coding - Mapping functionality
The Merge process ignores deceased indicator of source constituent
Roll-back functionality for the Constituent Merge process
Change site security to allow users to view but not edit constituents
Allow Constituents who are duplicated as Host and Attendee in the event registration process to be merged
Constituent Merge - Constituencies