# Hiding custom objects in the link structure || Use layering for custom objects

**URL:** <https://community.hubspot.com/t/hiding-custom-objects-in-the-link-structure-use-layering-for-custom-objects/74310>\
**Category:** HubSpot Ideas\
**Tags:** object\
**Created:** [February 2, 2023, 8:02am UTC](https://community.hubspot.com/t/hiding-custom-objects-in-the-link-structure-use-layering-for-custom-objects/74310 "2023-02-02T08:02:41Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![SignalsBy](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/signalsby/32/8540_2.png) [@SignalsBy](https://community.hubspot.com/u/SignalsBy)\
**Post date:** [February 2, 2023, 8:02am UTC](https://community.hubspot.com/t/hiding-custom-objects-in-the-link-structure-use-layering-for-custom-objects/74310/1 "2023-02-02T08:02:41Z")

</div>

Hi there,

We would like to see the option to hide custom objects in the link structure contacts - custom object - {hidden}

This can be done by following the rules in the permission sets with an additional checkbox if the custom object should be hidden or not by those users that does not have access.

Layering these custom objects would also be a perfect solution but has more development workload behind it (see screenshot attached)

{custom object #1}

{custom object #1.1}

{custom object #1.2}

{custom object #2}

{custom object #3}

Associations with the main #1 custom object {root} would need to be mandatory as a ground rule.

 ![Untitled.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/9/e/9ecaacb965980a0cf29fe1f4250ff9d66d796794.png)

This feature will add value to companies that work with customer- and partner sides at the same time, giving them the opportunity to structurize their CRM set up in a much cleaner way when it comes to the information flow between customer- and partner sides.

---

<div class="post-metadata">

**Author:** ![JPlaggenborg](https://avatars.discourse-cdn.com/v4/letter/j/c67d28/32.png) [@JPlaggenborg](https://community.hubspot.com/u/JPlaggenborg)\
**Post date:** [February 2, 2023, 10:08am UTC](https://community.hubspot.com/t/hiding-custom-objects-in-the-link-structure-use-layering-for-custom-objects/74310/2 "2023-02-02T10:08:30Z")

</div>

This is interesting for us as well!

---

<div class="post-metadata">

**Author:** ![LWiegers](https://avatars.discourse-cdn.com/v4/letter/l/f0a364/32.png) [@LWiegers](https://community.hubspot.com/u/LWiegers)\
**Post date:** [February 2, 2023, 12:32pm UTC](https://community.hubspot.com/t/hiding-custom-objects-in-the-link-structure-use-layering-for-custom-objects/74310/3 "2023-02-02T12:32:45Z")

</div>

Yes please!

---

<div class="post-metadata">

**Author:** ![DCarter9](https://avatars.discourse-cdn.com/v4/letter/d/49beb7/32.png) [@DCarter9](https://community.hubspot.com/u/DCarter9)\
**Post date:** [May 1, 2023, 11:36am UTC](https://community.hubspot.com/t/hiding-custom-objects-in-the-link-structure-use-layering-for-custom-objects/74310/4 "2023-05-01T11:36:32Z")

</div>

We could use this too.

---

<div class="post-metadata">

**Author:** ![EarlJ](https://avatars.discourse-cdn.com/v4/letter/e/9d8465/32.png) [@EarlJ](https://community.hubspot.com/u/EarlJ)\
**Post date:** [August 16, 2023, 12:10pm UTC](https://community.hubspot.com/t/hiding-custom-objects-in-the-link-structure-use-layering-for-custom-objects/74310/5 "2023-08-16T12:10:41Z")

</div>

Push!

---

<div class="post-metadata">

**Author:** ![April\_at\_Paubox](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@April\_at\_Paubox](https://community.hubspot.com/u/April_at_Paubox)\
**Post date:** [April 2, 2024, 4:44pm UTC](https://community.hubspot.com/t/hiding-custom-objects-in-the-link-structure-use-layering-for-custom-objects/74310/6 "2024-04-02T16:44:02Z")

</div>

Appreciate this suggestion - this would help Ops and Enablement a lot! All the menu items/functionality can be overwhelming for various departments, so hiding objects unrelated to roles may help “quiet the noise.” Also, the nesting of custom objects is a bonus and could help those who aren’t familiar with data models quickly visualize the custom objects hierarchy/connections

---

<div class="post-metadata">

**Author:** ![JCablePT](https://avatars.discourse-cdn.com/v4/letter/j/cc9497/32.png) [@JCablePT](https://community.hubspot.com/u/JCablePT)\
**Post date:** [May 22, 2024, 8:55am UTC](https://community.hubspot.com/t/hiding-custom-objects-in-the-link-structure-use-layering-for-custom-objects/74310/7 "2024-05-22T08:55:08Z")

</div>

This is essential as not all objects are relevant to all teams.