Views - Allow Super Admins the ability to edit and save any existing View, regardless of ownership
Would be nice for Super Admins to be able to edit and save any existing view, regardless of the owner/creator. You can only edit the views that are "Created by me".
For example if one Super Admin creates a "default" view for users, and it needs to be modified/updated, no other Super Admin can edit that View. They have to do a clone and save it as a new View.
Yes, you can clone the original which preserves the sharing, but if that View was bookmarked by any users, that bookmark is now broken. Same if the URL to the View was provided via email.
The ability to also change the "Manage Sharing" on existing views would be helpful also.
Additionally, the "Created by others" list doesn't show who created the View, so no way to contact the owner to ask them to make a change.
*Also, there is no good corresponding "Label" for the idea category for Views.
Any update here? Looks like a HubSpot employee commented on this over a year ago now and no movement has been made. Definitely a major oversight that makes it esentially impossible to fix views.
We need this too, it's so frustrating not being able to archive unused properties because they are in a view. And I wouldn't want to bother my reps with having to figure out how to edit their views, they sometimes didn't even include that property on purpose it was just on the view they started from.
Quick hack on this: you can duplicate the view, remove the property you want to delete and then delete the old version of the view. If the user wants to edit the view afterwards they just have to duplicate it again and let you know so you can delete your version then. Hope this helps some of you!
We desperately need this feature - especially in a tech business with a turnover! When someone in Operations who set these up leaves the business, we won't be able to edit any of the views which is a serious problem.
Hello, +1. This is a big issue currently in my company. We are classifying thousands of workflows and properties and we can't archive most properties because they are in views. We only can delete this views and we are not able to filter to see when this view was last viewed.
Super users, on top of full access to sharing options of views owned by others, if not, should have access to transfer ownership at the least. And please, add bulk actions to all views tool.
the first solution is the ability to delete views as a super admin - this is the quickest solution to get rid of a property you no longer want in a view
The second is the ability to log in as a user and edit a view - this is helpful for current reps that I know have strategically set up their views (this way I don't have to completely delete it I can just log in as them and edit the property I want to archive out of the view)
Thank you HubSpot for listening to your users and continuously improving!
Update: Solution I found for now is to log in as a user who is the owner of the view and then edit and save the view
It would help me with maintaining hubspot clean. For now it's problematic to clean properties, because some people are using the old ones in the views, and it's not possible to make them edit the views. Super needed feature and fairly easy to make I guess!
This seems like a no-brainer and a bit suprised this hasn't been released yet. Super Admin should be able to edit, delete and alter anything they see fit --regardless of ownership.
Managing custom created views (companies, tickets etc) is also quite challenging when a user is removed. When deactivating a user, there is also no prompt to assign ownership of these custom views to someone else.
This would be a really useful feature. As a super admin I have to delete views if I don't have the time to contact the person and ask them to amend their view. Also, where you have more than one person responsible for setting views, it makes it much simpler if any of the system admins can alter views rather than just the owner being able to. It causes a lot of issues if the owner is on leave or unavailable.
It is now May 2024 and there has been a consistent trail of comments for two years straight about how needed this is.
I am in the same situation as many others here- my users made views that use properties that I am now removing.
Instead of 1. Remove column from view 2. Delete property
The process looks more like 1. Clone view 2. Remove column from view 3. Delete old view 4. Delete property
- With the side effects of the user no longer being able to edit the columns in their own view.
This is such a messy process for no reason, as Super Admin should have u nlimited access within the account to do whatever they need. Why have we gotten features for content creating and editing and podcasting tools, but can't do simple things like this? You are developing in the wrong direction.
Adding my support to this. We have staff that are incapable of managing their own views and our property records are a mess that is irrepairable as a result. It is issues like this that continuously remind me that better CRM's must exist.
Let us remove properties from views in bulk without having to log in as the other user. Additionally, Super Admins should be able to edit eachothers views. Right now, I am having to turn Super Admin privledges on and off.
We would benefit from this, we have many views we use for reporting, and links to that view are in SOP documents, but if the user who created the view leaves the company and something happens and we need to edit or add to the view, you can't. So we have to delete the view, recreate it, and then go back and update the link in the SOP document. It is a lot of work for something that the super admins should be able to do as they should have edit access to everything.
I don't know why I didn't think of this before! I had a case where I urgently needed to remove some fields from a view created by another user and I couldn't get hold of them.
As I'm a super admin, I just logged in as them using the option in the users & teams section on their record and was able to make all the changes I needed to.
