Give admins the ability to delete or modify other's lists
Current state does not allow the admins to modify/delete lists that were created by other users, so if somebody leaves your organization their lists remain.
Admins should be able to delete lists to keep database clean and to ensure that "new" lists that are of similar nature are the ones being actively used. Old lists should be able to be deleted to avoid confusion.
Not being able to delete former employee lists is a HUGE problem in addition to having to open the list and click on dropdowns etc to delete the list. Too many clicks!
getting cluttered out here - especially with old employee lists. Admins should be able to anything and everything in the database. An enterprise-class database would have this ability.
Not just the ability but an easy way to delete - it's currently 8 clicks and 2 wait while loading to even delete my own. Why can't there be "x" function like there is on the list that is on main window???? Also need ability to delete those that created by former staff.
It's ridiculous that this hasn't been fixed yet. Admins need to be able to delete former employees' lists AND to be able to see who created a list. The way this is designed leads to clutter and decreased usability.
This is a HUGE issue and it seems insane that there isn't already a fix for this. Admins should be able to... administrate. Everything. When an employee leaves, it's hugely important to deactivate their account immediately for security purposes. Often the cleanup needs to come later. Our Lists are a mess of old lists that people need to sort through to find the lists they need.
One work around would be at least the ability to see who created a List but we can't do that either. Even if the ability to see that was just allowed by Administrators. Such a design unfortunately just promotes a messy database/platform. Please see https://renxt.ideas.aha.io/ideas/RENXT-I-3191 and vote for that item as well. We need to get those votes up to the same level as here.
One idea in the interim is to have a Naming convention that your user base follows that includes identifying her/himself like initials or name. Depending on any other conventions you may or may not have, it might be best for sorting to have that as the first part of the List name. Of course you can have them edit and clean-up (Delete unneeded Lists) on existing Lists. Overall though this should not be necessary as this as many have said here is basic database structure that we often take for granted as it appears to have been done in this design unfortunately.
This is a huge issue for us, especially when folks leave the organization and don't do a cleanup before they leave. I'm dealing with a huge amount of lists that date back 3 years and were created for specific event invitation emails and never used again. Since they created the lists with the "Others can view" option, I can't do any cleanup on them.
This have become a huge issue for our organization and the ability to be able to delete lists in RENXT, even if only at an Admin level, MUST be addressed quickly! Bad lists, accidental lists and even older lists that were made for past years are still visible and run the risk of being selected when trying to communicate with our stakeholders. While I also agree the create of folders would be nice, simply being able to delete lists is vital and necessary to proper database functionality!
This must be reviewed. Lists are a mess. 1. Bad list is created by a user who doesn't understand how to pull data. 2. Lists aren't put into folders - or organized in any way at all - nobody knows what list is good or bad or how many there are with the same name. 3. Bad list is picked up by other team members because of helpful sounding name. 4. Bad list is mailed to, reviewed for donations, causing bad faith in the data or worse - bad relations with donors. 5. List cannot be modified or deleted when noticed by the database manager - it just floats around waiting to be picked up again. I just had to email a user who is learning Raiser's Edge to disregard a list with a similar name because the data is bad - it sounds ridiculous. Of course when he searches for the list again there will be TWO because of inability to sort the lists.
This needs to added to the Admin's control. As the database manager, you need the ability to control the database and this makes for a very messy database list. This makes the Lists option in RENXT look out of control as anyone can just create a list. Then the person leaves the orgnization, and we as the database manager have no control to then "Clean" our database and maintain "Clean" lists. Please make this an option.
yes - when? also, delete multiple lists at once without opening each one!!
This is great. How will we do it?
[image: photo]
Cathi Christopher
Director of Accounts & Database Administration, GO Ministries, Inc
502-493-9846 | gomin.org
cchristopher@gomin.org
11501 Plantside Dr, Ste 14, Louisville, KY 40299
Create your own email signature
[image: __tpx__]
This is fantastic! A much needed option to keep data clean and to avoid confusion of using old lists. :-)
Yay! Hope we see this soon!
Allelujah. Thank you
This was picked up! That's amazing!
Admins should be able to delete lists to keep database clean and to ensure that "new" lists that are of similar nature are the ones being actively used. Old lists should be able to be deleted to avoid confusion.
At this point, no admins exist if only IT can delete lists created by a lower tiered user. That's a base requirement of an admin profile
Admins should absolutely be able to delete lists. It's actually ridiculous that we are not able to.
Not being able to delete former employee lists is a HUGE problem in addition to having to open the list and click on dropdowns etc to delete the list. Too many clicks!
getting cluttered out here - especially with old employee lists. Admins should be able to anything and everything in the database. An enterprise-class database would have this ability.
Not just the ability but an easy way to delete - it's currently 8 clicks and 2 wait while loading to even delete my own. Why can't there be "x" function like there is on the list that is on main window????
Also need ability to delete those that created by former staff.
It's ridiculous that this hasn't been fixed yet. Admins need to be able to delete former employees' lists AND to be able to see who created a list. The way this is designed leads to clutter and decreased usability.
This is a HUGE issue and it seems insane that there isn't already a fix for this. Admins should be able to... administrate. Everything. When an employee leaves, it's hugely important to deactivate their account immediately for security purposes. Often the cleanup needs to come later. Our Lists are a mess of old lists that people need to sort through to find the lists they need.
Please make this a priority.
One work around would be at least the ability to see who created a List but we can't do that either. Even if the ability to see that was just allowed by Administrators. Such a design unfortunately just promotes a messy database/platform. Please see https://renxt.ideas.aha.io/ideas/RENXT-I-3191 and vote for that item as well. We need to get those votes up to the same level as here.
One idea in the interim is to have a Naming convention that your user base follows that includes identifying her/himself like initials or name. Depending on any other conventions you may or may not have, it might be best for sorting to have that as the first part of the List name. Of course you can have them edit and clean-up (Delete unneeded Lists) on existing Lists. Overall though this should not be necessary as this as many have said here is basic database structure that we often take for granted as it appears to have been done in this design unfortunately.
An admin should have the abilty to clean up bad information to prevent further confusion-lists should be able to be controlled by the admin.
This is a huge issue for us, especially when folks leave the organization and don't do a cleanup before they leave. I'm dealing with a huge amount of lists that date back 3 years and were created for specific event invitation emails and never used again. Since they created the lists with the "Others can view" option, I can't do any cleanup on them.
This have become a huge issue for our organization and the ability to be able to delete lists in RENXT, even if only at an Admin level, MUST be addressed quickly! Bad lists, accidental lists and even older lists that were made for past years are still visible and run the risk of being selected when trying to communicate with our stakeholders. While I also agree the create of folders would be nice, simply being able to delete lists is vital and necessary to proper database functionality!
This must be reviewed. Lists are a mess.
1. Bad list is created by a user who doesn't understand how to pull data.
2. Lists aren't put into folders - or organized in any way at all - nobody knows what list is good or bad or how many there are with the same name.
3. Bad list is picked up by other team members because of helpful sounding name.
4. Bad list is mailed to, reviewed for donations, causing bad faith in the data or worse - bad relations with donors.
5. List cannot be modified or deleted when noticed by the database manager - it just floats around waiting to be picked up again.
I just had to email a user who is learning Raiser's Edge to disregard a list with a similar name because the data is bad - it sounds ridiculous. Of course when he searches for the list again there will be TWO because of inability to sort the lists.
This needs to added to the Admin's control. As the database manager, you need the ability to control the database and this makes for a very messy database list. This makes the Lists option in RENXT look out of control as anyone can just create a list. Then the person leaves the orgnization, and we as the database manager have no control to then "Clean" our database and maintain "Clean" lists. Please make this an option.