# Property access management

**URL:** <https://community.hubspot.com/t/property-access-management/123971>\
**Category:** Account & Settings\
**Tags:** enterprise\
**Created:** [January 15, 2025, 10:54am UTC](https://community.hubspot.com/t/property-access-management/123971 "2025-01-15T10:54:49Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mike533](https://avatars.discourse-cdn.com/v4/letter/m/54ee81/32.png) [@mike533](https://community.hubspot.com/u/mike533)\
**Post date:** [February 9, 2025, 4:40am UTC](https://community.hubspot.com/t/property-access-management/123971/5 "2025-02-09T04:40:12Z")

</div>

It appears that team-based limitations and property-specific permissions are at odds with one another in your access settings. Changing team access to permit more extensive changes while preserving property-specific restrictions is one way to solve the problem. In order to prevent problems with team ownership, if your system permits it, think about using role-based access instead of team-based access. As an alternative, see if it’s possible to establish a new permission set that allows cross-team adjustments without granting complete access to every contact. Finding a solution could also be aided by looking at the support documentation and permission hierarchy in your CRM.

---

_[View the full topic](https://community.hubspot.com/t/property-access-management/123971)._