# Hide, delete and edit default HubSpot property fields

**URL:** <https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281>\
**Category:** HubSpot Ideas\
**Tags:** object\
**Created:** [June 7, 2017, 10:19am UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281 "2017-06-07T10:19:22Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michiel](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/michiel/32/99730_2.png) [@Michiel](https://community.hubspot.com/u/Michiel)\
**Post date:** [June 7, 2017, 10:19am UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/1 "2017-06-07T10:19:22Z")

</div>

HubSpot offers a lot of default property fields, but not all of them are relevant and useful for all users when creating new contacts or editing/adding data on existing contacts.

There currently isn’t a way to limit property access other than on an all-or-nothing scale. So the fields will have to all be visible. Also it’s not possible to edit the names.

To make this more flexible and user friendly, I prefer HubSpot to add a possibility to hide, delete and edit the names of default HubSpot property fields for different user levels/groups. In this way we can better arrange showing only relevant fields to users, without confusing and bothering them with all kind of unnecessary fields.

Please let me know your thoughts on this and support this idea when you also agree this is a ‘need to have’ addition.

Thanks

Michiel

---

<div class="post-metadata">

**Author:** ![kimnguyen](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/kimnguyen/32/99678_2.png) [@kimnguyen](https://community.hubspot.com/u/kimnguyen)\
**Post date:** [June 14, 2017, 6:55am UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/2 "2017-06-14T06:55:19Z")

</div>

Hi,  
One temporary trick would be to create a new custom field that matches your requirements, and then creating a workflow that would copy all existing entries to that new field?  
Best Regards,  
Kim Nguyen  
[www.elixir-solutions.be](http://www.elixir-solutions.be)

---

<div class="post-metadata">

**Author:** ![lcrumling](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lcrumling/32/86419_2.png) [@lcrumling](https://community.hubspot.com/u/lcrumling)\
**Post date:** [September 7, 2017, 5:47pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/3 "2017-09-07T17:47:53Z")

</div>

Agree, I hate that I can’t delete the irrelevent HubSpot-created properties (or at least hide them)!

Editing would be nice too - there are some that I could actually use if I could add/delete an option or two.

---

<div class="post-metadata">

**Author:** ![Jack](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jack/32/77566_2.png) [@Jack](https://community.hubspot.com/u/Jack)\
**Post date:** [September 13, 2017, 6:56pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/4 "2017-09-13T18:56:26Z")

</div>

Totally agree!

---

<div class="post-metadata">

**Author:** ![pauloxm](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pauloxm/32/52876_2.png) [@pauloxm](https://community.hubspot.com/u/pauloxm)\
**Post date:** [September 13, 2017, 7:24pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/5 "2017-09-13T19:24:52Z")

</div>

Remove this feature, let us edit or delete it.

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [September 17, 2017, 11:46pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/6 "2017-09-17T23:46:31Z")

</div>

Agree! Would be great to at least edit the HubSpot properties. That way it would always be possible to repurpose the field if not relevant.

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [October 16, 2017, 7:08pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/7 "2017-10-16T19:08:39Z")

</div>

Totally agree, we need a Business Address, Residential, and delivery address. Having the default vauge “Street Address” property is counterproductive.

---

<div class="post-metadata">

**Author:** ![nishansingh1](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/nishansingh1/32/9140_2.png) [@nishansingh1](https://community.hubspot.com/u/nishansingh1)\
**Post date:** [December 17, 2017, 10:25pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/8 "2017-12-17T22:25:45Z")

</div>

Totally agree. At the very least, I should be able to hide the properties that I don’t need.

---

<div class="post-metadata">

**Author:** ![jewsbur0](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jewsbur0/32/30597_2.png) [@jewsbur0](https://community.hubspot.com/u/jewsbur0)\
**Post date:** [May 11, 2018, 12:03pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/9 "2018-05-11T12:03:07Z")

</div>

This is so very annoying! We’ve just rolled out this to our commercial team and there are so many irrelevant fields. Quite disapointing!

---

<div class="post-metadata">

**Author:** ![CRMGuru](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/crmguru/32/88643_2.png) [@CRMGuru](https://community.hubspot.com/u/CRMGuru)\
**Post date:** [May 16, 2018, 6:29pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/10 "2018-05-16T18:29:10Z")

</div>

We absolutely need to hide Hubspot fields. There are over 100 default fields and it is very difficult to find amongst hundreds of our own fields.

---

<div class="post-metadata">

**Author:** ![lilybond](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lilybond/32/42653_2.png) [@lilybond](https://community.hubspot.com/u/lilybond)\
**Post date:** [May 18, 2018, 9:04pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/11 "2018-05-18T21:04:23Z")

</div>

This would be extremely helpful! It’s extremely confusing to have these fields, which we never use, in addition to our (often similar) fields.

---

<div class="post-metadata">

**Author:** ![system](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/system/32/124_2.png) [@system](https://community.hubspot.com/u/system)\
**Post date:** [May 29, 2018, 11:43am UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/12 "2018-05-29T11:43:04Z")

</div>

Hi

Similar but we would like to be able to add a custom field and then choose if someone has access to it I.E read only view.

There is information we store that we may not wish for a normal user to be allowed to edit as it could be tied to a workflow!

---

<div class="post-metadata">

**Author:** ![quaetapo](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/quaetapo/32/32969_2.png) [@quaetapo](https://community.hubspot.com/u/quaetapo)\
**Post date:** [May 31, 2018, 6:46am UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/13 "2018-05-31T06:46:38Z")

</div>

Totally agree, along with being able to determine which users can see properties or properties groups to give added security to the data.

---

<div class="post-metadata">

**Author:** ![pd-viz](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pd-viz/32/101739_2.png) [@pd-viz](https://community.hubspot.com/u/pd-viz)\
**Post date:** [June 22, 2018, 4:04pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/14 "2018-06-22T16:04:20Z")

</div>

Plus one for this idea. Maybe these fields can be part of a profile, and there can be multiple profiles with different amount and kinds of fields, so a user can choose it upon startup.

---

<div class="post-metadata">

**Author:** ![pauloxm](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/pauloxm/32/52876_2.png) [@pauloxm](https://community.hubspot.com/u/pauloxm)\
**Post date:** [June 23, 2018, 5:36am UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/15 "2018-06-23T05:36:10Z")

</div>

I gave up on HubSpot CRM, I’m using ProsperWorks and it’s way better.

---

<div class="post-metadata">

**Author:** ![HargerHoweAdv](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/hargerhoweadv/32/84335_2.png) [@HargerHoweAdv](https://community.hubspot.com/u/HargerHoweAdv)\
**Post date:** [July 16, 2018, 1:10pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/16 "2018-07-16T13:10:16Z")

</div>

Hi - for some reason I can’t upvote this. Several of our current clients want this ability (hide, edit and sort properties) to tailor the CRM to their industry jargon. Please add!

---

<div class="post-metadata">

**Author:** ![richdando](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/richdando/32/95715_2.png) [@richdando](https://community.hubspot.com/u/richdando)\
**Post date:** [November 6, 2018, 11:18am UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/17 "2018-11-06T11:18:05Z")

</div>

I completely agree. Our sales teams find it incredibly frustrating to have so many fields on show (many of which aren’t used nor relevant to their role).

---

<div class="post-metadata">

**Author:** ![bobj](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bobj/32/2490_2.png) [@bobj](https://community.hubspot.com/u/bobj)\
**Post date:** [November 9, 2018, 10:43pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/18 "2018-11-09T22:43:15Z")

</div>

Everyone seems to agree - including me. Some of the default fields are worthless and the clutter created makes analysis more difficult than it should be. What is Hubspot’s view? Is this an RFE tied to a release or in backlog??

---

<div class="post-metadata">

**Author:** ![Dylan](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/dylan/32/992_2.png) [@Dylan](https://community.hubspot.com/u/Dylan)\
**Post date:** [December 6, 2018, 1:53pm UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/19 "2018-12-06T13:53:48Z")

</div>

Hi HubSpot Community,

Thank you for your feedback on this issue! We’re listening and I did want to reach out with an update here - we have enabled the ability to re-group default HubSpot properties.

Now, you can greate a group titled, for example, “unused” and file your unused default HubSpot properties there. This should help provide you a cleaner properties experience. Thank you for your continued input!

Dylan

---

<div class="post-metadata">

**Author:** ![bobj](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bobj/32/2490_2.png) [@bobj](https://community.hubspot.com/u/bobj)\
**Post date:** [December 17, 2018, 11:19am UTC](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281/20 "2018-12-17T11:19:46Z")

</div>

Hi Dylan - thanks for moving this forward. I just tried moving a few unused properties and 90+% of them are locked by the system. Is it possible to navigate around this?

[Next page](https://community.hubspot.com/t/hide-delete-and-edit-default-hubspot-property-fields/2281.md?page=2)
