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
- Go to Settings > Data Management > Properties and pick the object.
- Hover over the property, click More and choose Manage access. For several properties, select them and click Manage access above the table.
- Choose an access option. For read-only fields maintained by finance or an integration, Allow everyone to view is usually right.
- Save, then test with a user who should be restricted.
- Check workflows, reports and dashboards that use the property, since restricted users may not be able to load them.
- 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 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, 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 and what Projects can and can’t build.
Sources
- Restrict view and edit access for properties (HubSpot Knowledge Base)
- HubSpot user permissions guide (HubSpot Knowledge Base)
- Projects capabilities (Jetstack AI documentation)
- General data points (Jetstack AI documentation)
Checked October 30, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.
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