HubSpot permission sets let admins define a reusable group of access controls, then apply that group to any user in the portal. Instead of configuring each person’s permissions from scratch, you build the set once and assign it to everyone in the same role. This guide covers how they work and how to set them up.
From your HubSpot portal, click the settings icon in the top navigation. Under Account Setup, go to Users and Teams. Open the Permission Sets tab.
Click Create permission set and give it a name that reflects the role, such as “Sales Rep”, “Marketing Manager”, or “Read-Only Finance”. Names make it faster to assign the right set when onboarding new team members.
Permission sets are organised by object type and action. For each object area in the portal, choose the appropriate access level: from full edit rights down to view-only or no access at all. You can also control which record properties each role can see or modify.
In the Users tab, select the user and apply the permission set. You can assign a set when adding a new user or update an existing user at any time. Changes apply immediately.
Log in as a test user or use HubSpot’s built-in user impersonation (where available) to confirm the role can do what it should and cannot do what it should not. Catching a misconfigured set before rollout saves a support ticket later.
What is the difference between permission sets and standard user permissions?
Standard HubSpot user permissions are set individually for each user. Every time you add someone, you tick boxes for what they can and cannot access. This works fine for a team of five. For larger teams, it creates inconsistency: two sales reps with nominally the same role end up with different permissions because a different admin configured each one.
Permission sets solve this by turning a role’s access profile into a named, reusable template. When you hire a sixth sales rep, you assign the “Sales Rep” set rather than rebuilding the configuration manually. If you need to add a new access level to the whole sales team, you update one set instead of updating every individual.
Permission sets are available on HubSpot Professional and Enterprise plans. The exact features within a permission set depend on which Hubs are active in the portal.
When should you use permission sets?
Permission sets are worth setting up when two or more people share the same role and need the same access. For most teams this applies to:
- Sales teams: Reps need deal and contact access but should not edit marketing workflows or billing settings.
- Marketing teams: Need access to campaigns and email content but not the sales sequences or quote tools.
- Customer support: Need ticket and inbox access, possibly with read-only view of deal history, but no edit rights on deal stages.
- Finance or operations stakeholders: Need reporting access without the ability to modify contacts or pipelines.
If every person in the portal has a unique role with unique access needs, standard user permissions may be sufficient. Permission sets add the most value where team roles are consistent.
How do permission sets interact with teams in HubSpot?
HubSpot teams and permission sets serve different purposes. Teams control which records a user can see based on ownership and assignment. Permission sets control what actions a user can take across the portal regardless of ownership.
A sales rep on the Bangkok team may be restricted to only seeing deals assigned to Bangkok team members. Their permission set controls what actions they can take on those records, such as editing deal stages or viewing reports. The two settings work alongside each other rather than replacing each other.
For most portals in Southeast Asia, setting up teams first and then layering permission sets on top gives the cleanest result: regional data visibility controlled by teams, role-based actions controlled by permission sets.
Can you override a permission set for one user?
Yes. HubSpot allows individual permission overrides on top of an assigned permission set. If a specific user needs one additional access right that the rest of the team does not need, you add that override without creating a separate permission set for just that person.
Overrides are visible in the user’s individual permission view, so admins can see at a glance where someone’s access differs from the standard set. This keeps the audit trail clean without forcing you to create a separate set for every edge case.
What happens when a permission set is updated?
Changes to a permission set apply immediately to every user assigned to that set. There is no need to go through each user individually. If you remove access to a feature, all users on that set lose access when the set is saved. If you add access, all users gain it.
This is the main operational advantage for growing teams. When HubSpot releases a new feature or when a process changes, one update to the set propagates to the whole group.
Are there limits on the number of permission sets you can create?
HubSpot does not publish a hard cap on the number of permission sets per portal, but in practice most portals need five to ten sets at most. Creating too many sets defeats the purpose: if you have a unique set for each person, you are back to managing permissions individually.
A useful approach is to map roles to sets before creating them. List every distinct job function in the portal and define the access each one needs before creating the sets. Starting from roles rather than from individuals keeps the list manageable.
How do permission sets affect the HubSpot user roles feature?
HubSpot also has a separate “Roles” concept in Enterprise accounts. It operates at a higher level than permission sets and covers things like super admin authority and account billing visibility. Roles and permission sets are distinct but complementary. Roles define the account-level authority; permission sets define the day-to-day CRM and marketing access.
For most Southeast Asian businesses on Professional plans, permission sets alone are sufficient for access management. Enterprise customers dealing with larger teams across multiple regions benefit from combining the two.
Related guides
If you are building out your HubSpot access management setup, these guides cover the adjacent topics:
- HubSpot User Permissions: How to Control Access in Your CRM
- HubSpot Teams: How to Organise Your CRM Users and Manage Access by Team
- HubSpot Super Admin: How to Manage Account-Level Settings
Frequently asked questions
Are permission sets available on all HubSpot plans?
Permission sets are available on Professional and Enterprise plans. Free and Starter users manage permissions individually per user without the reusable set feature.
Can a user be assigned more than one permission set?
No. Each user can have one permission set assigned at a time, with individual overrides added on top if needed. If a user’s role spans multiple departments, create a custom set that covers their specific combination of access.
What happens if I delete a permission set?
If you delete a permission set, the users assigned to it revert to the default HubSpot user permissions. It is good practice to reassign users to a different set before deleting the old one.
Can permission sets be exported or copied between portals?
HubSpot does not support direct export or copy of permission sets between portals. If you manage multiple portals, you will need to recreate the sets in each one.
Do permission sets work with HubSpot’s sandbox account?
Yes. You can set up and test permission sets in a sandbox account before applying the configuration to your production portal.
This is an independent informational resource produced by a HubSpot Platinum Partner. HubSpot is a trademark of HubSpot, Inc.
Planning a HubSpot setup or integration in the region?
Contact us