The ability to approve or deny user profile changes with additional space for annotation
For internal purposes only, we would love the ability to view profile changes and either approve or deny them. In addition, we need space where we can note why the change was not made.
-
Sondra Berry
- Dec 13 2018
- Under consideration
Related ideas
We should have the ability to annotate ALL changes, not just the approved ones.
This is related to a post in community that was started in 2015 and was just added to this morning: Re: Unexplained Profile change results in Core . Certainly a more robust "handle profile changes" would be of great help to platform managers and I wish it would move up in terms of priorities. Janet - 2018 was a LONG time ago! And with the institution of Blackbaud ID the need to have different emails for each record is now imperative.
I know your inquiry was to Sondra, but one example where contact info changes would be denied is for email addresses. At our school sometimes one parent will put their email on every record in the family. Would love to deny a change like this rather than fine-tuning the permissions for that data field.
Very helpful, Thank you! some of this stuff we could never make up on our own!
Hi Sondra,
We've been looking into an update for Handle Profile Changes; as you know, today this is just a view into the history log for what has changed. Can you add some more information here about the kinds of changes that wouldn't be approved? It is unlikely we will build in a 'staging' area to keep changes before they are approved. However, we are weighing the relative priority of better sorting or filtering on the page, adding notifications, or removing the need for taking action on records except those done by users of a certain role, or changes TO those users of certain roles (e.g. parents)