I agree. The ability to edit tag would revolutionize how our development department uses Raiser's Edge. The current tag assigned by RE is just useless to us.

For anyone looking back at this post that wants to HIDE TAGS. You can bypass what Blackbaud has failed to do with a Chrome Extension. I personally use UBlock Origin, but I'm sure there are others that do the same.

UBlock Origin by default acts as an ad blocker, but you can customize it to block specific areas on specific websites, such as tags in RE: NXT

To hide RE: NXT tags with UBlock Origin:

https://www.freecodecamp.org/news/how-to-block-content-from-web-pages-using-ublock-origin

The section labeled: "How to Filter HTML Elements" will explain how to do this.

Note: This does not remove the tags, it simply hides them so they don't take up the extra workspace that so many people have had trouble with.

Feel free to copy/paste any of this if it helps you or your colleagues.

I also agree the tags as is are not useful for our org - the ability to customize or turn this section off in the work center is needed. Our fundraisers hate it and it is a small but important thing that turns them off from using the system.

Yes, please! It would be great to be able to create our own tags; we largely ignore the existing ones.

It would also be beneficial to set criteria for tags, such as "Head of Household" and "Any gift Credit". We are finding that some households give through DAFs and will only ever be soft credited, so they have incorrect tags. At the same time, we place actions solely onto the Head of Household, so we would like to be able to hide spouses from the "Needs Attention" section.

Yes - please!

Some of them don't really apply, such as the "overdue pledge". That warning seems to be based on an installment being fulfilled completely, and when donors transfer stock as a pledge payment, the proceeds do not always fulfill an installment. Others just are not relevant to every organization.

The smart tags are a great idea IF they can be customized by the clients. Everyone I work with has basically overlooked them. So once they become relevant, it will be more work to remind staff to pay attention to them,.

More customization and individualization options are always useful.

Yes, if we could customize the criteria for tags, that would be great. Fundraisers don't need a tag every month for every recurring gift! It makes more work for them so they just ignore the tags altogether, making them worse than useless.

It's really confusing to see all of the "no contact" or "lapsed donor" or whatever other Needs Attention on organizational records and their contacts because the contact is only soft credited, but all the actions and opportunities are with the contact, not the org. It seems like it would be a lot easier to customize or disable the Needs Attention than to completely change the way actions, opportunities, and gifts work for soft credits/relationship records and org contacts.

We are using NXT with our parent solicitors (a group of 120!), and we would really prefer they not see some of the info the Tags are pointing out (such as "High Wealth Rating". It would be really helpful if there was a way to turn off access to those tags for certain security groups. Since we can set the Ratings not to show up, why not the Tags?

I actually just want to be able to turn them off. They really don't add anything.

A list of options similar to those when managing e-mail was available this would be useful - read, dismiss, move to back of queue, remind me in a week - quick drop down of system actions to take.

Set it up as Business Rules.  Each org can then determine what Tags are used, how they're calculated, and what records they apply to (i.e. if you want to see Tags only on Individual Records or only on Records with Gifts, or Gifts of a certain amount).  Then, for those that want a more out of the box product, have defaults for each Rule.

I would also like the option to turn tags off!

This would be a work-around for another need -- creating an NXT list directly from a static query in the database view.