---
title: "Can you restrict access to HubSpot properties? · Jetstack AI"
description: "How to restrict access to HubSpot properties by user or team: the Enterprise requirement, the four access options, and why it isn't a security control."
url: "https://jetstack.ai/answers/restrict-hubspot-property-access/"
---

# Can you restrict access to HubSpot properties?

Yes, on Enterprise. A Super Admin can restrict access to HubSpot properties from Settings > Properties: hover over the property, click More, choose Manage access, and make it private to Super Admins, viewable by everyone but editable only by Super Admins, or assigned to specific users and teams. HubSpot warns it isn't a complete security measure, because anyone can still set restricted properties through the API.

![](https://jetstack.ai/images/authors/aditya-kumar.webp)

By [Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/) Founder, Jetstack AI

Updated October 30, 2026

On this page

## What HubSpot supports natively

| Topic        | What HubSpot says                                                                                          |
| ------------ | ---------------------------------------------------------------------------------------------------------- |
| Subscription | Enterprise (Marketing, Sales, Service, Data, Content or Revenue Hub)                                       |
| Permissions  | Super Admin to restrict a property                                                                         |
| Objects      | Contact, company, deal, lead, ticket and custom object properties                                          |
| Exceptions   | Some properties can’t have view access restricted, such as Email, Deal name and Ticket status              |
| API          | All users can still set or edit restricted properties through the API, and when manually creating a record |
| Super Admins | Can’t be restricted                                                                                        |

**The four access options:**

| Option                          | Who can view                                             | Who can edit |
| ------------------------------- | -------------------------------------------------------- | ------------ |
| Allow everyone to view and edit | Everyone                                                 | Everyone     |
| Allow everyone to view          | Everyone                                                 | Super Admins |
| Private to Super Admins only    | Super Admins                                             | Super Admins |
| Assign to users and teams       | Per user or team: view and edit, view only, or no access |              |

Granting access to a nested team also gives its parent team the same access. Users without view access see a restricted-access icon instead of the value and can’t see records in saved views filtered by that property.

## How to restrict access to HubSpot properties

1. **Go to Settings > Data Management > Properties** and pick the object.
2. **Hover over the property**, click **More** and choose **Manage access**. For several properties, select them and click **Manage access** above the table.
3. **Choose an access option.** For read-only fields maintained by finance or an integration, *Allow everyone to view* is usually right.
4. **Save, then test** with a user who should be restricted.
5. **Check workflows, reports and dashboards** that use the property, since restricted users may not be able to load them.
6. **Restrict the object or tool too** if the data is truly sensitive. HubSpot recommends this because property restrictions don’t stop API writes.

## Common mistakes

- **Treating restriction as security.** For regulated data, use HubSpot’s Sensitive Data settings (Enterprise) and object-level permissions.
- **Restricting a property a team’s dashboard uses.** Their reports stop loading.
- **Forgetting new team members.** Team-based access is easier to maintain than per-user lists.

## Where Jetstack AI fits

Jetstack AI’s [Portal Audit](https://jetstack.ai/audit) gives you the full picture before you lock anything down. Its Property Management block reads every contact, company, deal and ticket property and **lists each one HubSpot has marked sensitive or highly sensitive**, next to unused properties, missing descriptions and naming problems. Its User Management block scores who holds the keys: Super Admin count and ratio, inactive users and users without a defined role, plus, with the Chrome extension, two-factor coverage, partner users and 30 days of permission changes from the audit log. You decide which properties to restrict with all of that in one report. For the object and tool restrictions HubSpot recommends, [Projects](https://jetstack.ai/build), currently in limited release, builds permission sets from your existing roles. Who can view or edit a specific property stays a **You do this** step with instructions. See the [General data points](https://jetstack.ai/docs/audits/data-points/general) and [what Projects can and can’t build](https://jetstack.ai/docs/projects/capabilities).

## Sources

- [Restrict view and edit access for properties (HubSpot Knowledge Base)](https://knowledge.hubspot.com/properties/restrict-view-edit-access-for-properties)
- [HubSpot user permissions guide (HubSpot Knowledge Base)](https://knowledge.hubspot.com/user-management/hubspot-user-permissions-guide)
- [Projects capabilities (Jetstack AI documentation)](https://jetstack.ai/docs/projects/capabilities)
- [General data points (Jetstack AI documentation)](https://jetstack.ai/docs/audits/data-points/general)

Checked October 30, 2026. HubSpot changes its products often; tell us at <team@jetstack.ai> if something here is out of date.

![Aditya Kumar](https://jetstack.ai/images/authors/aditya-kumar.webp)

About the author

[Aditya Kumar](https://jetstack.ai/authors/aditya-kumar/)

Founder, Jetstack AI

Aditya Kumar is the founder of Jetstack AI, the AI platform HubSpot partners and RevOps teams use to audit portals, build implementations and reuse their best setups across portals. He writes about HubSpot architecture, automation and AI from the work of building it.

[More from Aditya](https://jetstack.ai/authors/aditya-kumar/) [LinkedIn](https://www.linkedin.com/in/aditya-ambrstack/)

HubSpot admin

## Turn the brief into approved HubSpot assets.

Projects plans the build against the client portal, generates the assets and deploys them only after you approve.

[Explore Projects](https://jetstack.ai/build)

On this page

HubSpot admin

## Related questions.

Can you restrict access to HubSpot properties?

Yes, on Enterprise. A Super Admin can restrict access to HubSpot properties from Settings > Properties: hover over the property, click More, choose Manage access, and make it private to Super Admins, viewable by everyone but editable only by Super Admins, or assigned to specific users and teams. HubSpot warns it isn't a complete security measure, because anyone can still set restricted properties through the API.

Can I restrict who sees a property on a Professional subscription?

Property view and edit restrictions need an Enterprise subscription. On lower tiers, limit access to objects and tools through user permissions instead.

Can I restrict access for another Super Admin?

No. Super Admins can always see and edit every property, regardless of restrictions.

Will a restricted property break workflows or reports?

It can. HubSpot notes that workflows using restricted properties may be affected, and reports or dashboards may fail to load for users who can't view a property they use.
