Back to Blog
HubSpotRevOpsCRM

HubSpot User Permissions: A RevOps Setup Guide by Role

Abhishek Singla Nov 17, 2026 19 min read
The short answer

Roles, then access

Decide the roles before anyone opens settings. On Enterprise, give each role a permission set. On Professional, start from a role template and keep those grants aligned by hand, because saving a permission set needs Enterprise. Use teams to draw the boundary HubSpot calls Their team's records, lock the few properties the property screen will let you lock, and keep Super Admin to a few named people.

Most of the work on HubSpot user permissions happens before anyone opens settings. In our CRM and RevOps work the role list is agreed before the first invite, so each new user lands on a defined grant. We set out that build order in the HubSpot implementation guide. This page is the access model that order depends on.

Cover for the HubSpot user permissions guide. Decide the roles first, then give each role one permission set and a team boundary.

How HubSpot permissions fit together

A seat and a permission answer different questions. Seats decide which tools a user can open, and permissions decide what they can do there, such as view, edit or delete (assign and manage seats, checked 17 Nov 2026). A permission set is a saved bundle of those actions. A team decides which records count as Their team's, a property restriction sits on one field, and Super Admin is the account-wide grant.

The permissions guide is on all products and plans. Super Admin, or a user with Add and edit users, can customise permissions. Someone with Add and edit users can only grant permissions they already hold (user permissions guide, updated 13 Nov 2026).

Layer What it controls Tier, as the article states it Who sets it
Seat Which subscription tools open Starter, Professional and Enterprise, on the seats model. View-Only and Core on those tiers. Sales, Service and Revenue seats on Professional or Enterprise for that hub Super Admin, or Modify billing
Permission View, edit, create, delete, export, and each tool switch All products and plans Super Admin, or Add and edit users, limited to permissions they hold
Permission set One reusable grant. Assigning it replaces that user's own permissions Enterprise on Marketing, Sales, Service, Data, Content or Revenue Hub. Up to 100 sets Super Admin creates and edits. Add and edit users assigns only a set they already hold
Role template A job-function starting point, copied onto the user The add-users article does not name a separate tier Whoever can edit that user's permissions
Preset Defaults: home screen, dashboard and language Professional or Enterprise to assign A user with the Presets permission
Team Which records count as Their team's, plus team reports and routing Professional or Enterprise to create. Enterprise to nest. An extra team needs Marketing, Sales or Service Hub Professional or Enterprise Super Admin or Add and edit users places someone. Add and edit teams organises teams
Property access Who can view or edit one property on a record Enterprise Super Admin
Asset access Who can open a listed asset, including workflows and segments. This can override permissions Workflows and segments need Enterprise. Other assets follow the assets article Depends on the asset. A Super Admin can still view a restricted asset
Super Admin The tools and settings in the permissions guide. Paid Sales or Service features still need that seat On a paid subscription, a Core, Sales or Service seat. A View-Only seat cannot be Super Admin Only a Super Admin

Presets get mixed up with permission sets. Assigning a preset needs Professional or Enterprise. Saving a permission set needs Enterprise (add and update HubSpot users, updated 8 Nov 2026). The Presets permission, in the permissions guide, is the home screen, the dashboard and the language. It does not hold the grant.

The seats model applies to accounts and subscriptions created after 5 March 2024. An older account that has not migrated only has the purchased Sales or Service seats from the previous model, and its add-user flow does not show Assign a seat (seats). Current seat prices stay on the HubSpot pricing guide.

View-Only seats are free and unlimited on Starter, Professional and Enterprise. That user can view records, dashboards and reports, filter reports, and log notes. They cannot edit records, save reports, change settings, create content, log email, or be a Super Admin. A Core seat opens the core tools of the subscriptions you bought. On Sales Hub Starter and Service Hub Starter, Core is how those hub features open. A Sales seat, on Sales Hub Professional or Enterprise, opens the features included with that hub. A Service seat does the same for Service Hub (seats). We cover what those hubs are for in a B2B team in the Sales Hub guide.

Changing the seat does not rewrite the toggles, so moving someone from a Sales seat to a Core seat closes Sales Hub features even when the permission is still on. A permission set can be assigned with no seat, and access is then whatever the set and the seat both allow. Copying permissions does not copy a paid seat, so assign the seat first (permission sets, updated 8 Sep 2026). Reassigning a seat does not restore Super Admin. The seats article states one exception: when a Super Admin transfers their only Core seat, Super Admin moves with it (manage user permissions, updated 3 Nov 2026, seats).

Record scope uses the current labels. View is All, Their team's, or Their, with the object name filled in: All contacts, Their team's contacts, Their contacts. Edit and delete add None. Merge is its own dropdown on contacts, companies, deals, tickets and custom objects. The Unassigned checkbox, on Their team's or Their, includes records with no owner. Ownership follows the default owner property and any custom property of the HubSpot user field type. Their team's means records owned by members of the user's teams, and of teams nested under them where nesting exists (user permissions guide).

Two lines on that page change a "delete none" design. Users with Edit can still delete activities on a record, and users with View can still create notes or tasks. Logging an email, call or meeting needs Communicate, and bulk delete is its own switch. Create covers records the user makes, including imports. HubSpot says it does not apply to records created by workflows, forms, the inbox, email logging, or Salesforce imports (user permissions guide).

Teams need Professional or Enterprise on Marketing, Sales, Service, Data, Content, Smart CRM or Revenue Hub, and nesting a team under a parent needs Enterprise. The parent can see what the teams under it own, and the nested team cannot see everything the parent owns. An extra team, on top of the main team, needs Marketing, Sales or Service Hub Professional or Enterprise. An extra member can open the team's records and is left out of that team's reports, routing rules, team notifications other than form notifications, workflow rotation and custom record views (create and manage teams, updated 29 Sep 2026). Change a record's owner and the HubSpot team property fills with the new owner's main team.

Limited asset access can override the permission toggles (manage user permissions). Workflows and segments need Enterprise before you can limit them. A workflow assigned to a team is limited to that team. A workflow with no assignment stays open to anyone with the workflows permission. A Super Admin can still view a limited asset. Blog posts and pages can be limited by team on Content Hub or Marketing Hub Enterprise (limit access to assets, updated 30 Sep 2026).

Decide the roles before you touch settings

Ask the same questions for every role: which records they can view, edit and delete, whether they can export, and which properties they can change. The grid is a starting point we use for a B2B revenue team. HubSpot does not publish a role matrix.

A sales development rep (SDR) or business development rep (BDR) works the top of the book. An account executive (AE) owns deals. Around them sit a sales manager, marketing, customer success, a finance or operations viewer, a RevOps admin, and the integration users that write when nobody is at the keyboard.

Role Records Export What we hold back
SDR or BDR View the team's contacts and companies. Edit their own. Delete on None Off Owner and lead status. Lifecycle stage stays visible
AE View the team's deals. Edit their own. Delete on None Off Deal amount. Stage and close date stay visible
Sales manager View and edit the team's deals and contacts. Delete on None Off, or on with Approve exports held elsewhere Scope stays Their team's
Marketing View contacts wide enough to build segments. Edit the properties marketing owns. Delete on None Off, or with approval Deal amount, and workflow Publish
Customer success View the team's companies and tickets. Edit their own. Delete on None Off Deal amount and close date
Finance or ops viewer View-Only seat when the job is to look. No record edit Off The seat blocks edits, saved reports and Super Admin
RevOps admin Edit on the objects they maintain. Delete on None unless a named cleanup needs it On Billing, unless they own the contract. Super Admin stays separate
Integration user Edit only the objects the job writes. Create on for those objects. Delete on None Off App Marketplace, user admin, Super Admin

An SDR with Edit on every contact can change lifecycle stage on any contact in the portal, so we start with Their team's view, Their edit, and Delete on None. Turn Unassigned on only for the person who clears a shared queue. With it off, a record with no owner drops out of their index, their segments and their reports.

An AE should see the team's deals, so a colleague's opportunity on the same account is visible, and should edit their own. The manager gets Their team's on view and edit, because All with Edit is the whole portal, and Export stays off for reps. Where a manager must pull a list, Export can be on, Export without approval stays off, and Approve exports sits with a Super Admin or the RevOps admin. Those are three switches (user permissions guide).

Marketing usually needs a wider contact view than a rep, because a segment built from Their contacts misses everyone else. That view still leaves deal amount and workflow Publish alone. Workflows have View, Edit, Publish, Enroll and Delete. Edit without Enroll means the user can change a workflow and still cannot enroll records.

A View-Only seat fits finance when the job is to look and filter. The moment they need a saved report, the seat is wrong, because View-Only cannot save reports. They then need a paid seat, Reports access at view, and record Edit left off. Customer success follows the AE pattern on companies and tickets.

The RevOps admin needs Edit property settings, which creates and edits properties and pipelines. Super Admin is a separate decision. On a move into HubSpot, including from Salesforce, rebuild these roles in HubSpot's seats and sets. We map the objects in the Salesforce to HubSpot migration guide, and the work around that move sits on HubSpot migration. Reps who cannot see the account they are working will keep the work somewhere else, which we describe in the adoption guide.

Set it up in HubSpot

Teams first, then the grant, then the user and the seat, then the properties. A Their team's option with no teams behind it does nothing.

  1. Create the teams. Settings, Users & Teams, Teams, Create team. Name it. On Enterprise, tick Put this team under another team and choose the parent. Add members and save. For one person, open the user, Setup, Teams, and set the Main team. Use Extra teams only when that subscription allows it (teams). Match teams to the books you already route and report. A person placed on a parent team sees every team underneath.

  2. On Enterprise, create the set. Settings, Users & Teams, Permission Sets, Create Permission Set. Name it for the role. Under Choose how to set access, use Start with a template or Start from scratch. Leave Make Super Admin alone. Set View, Edit, Delete and the tool switches, review, and create. Assign it now, or later: select the users, More, Assign Permission Set, Save. Editing a set updates everyone on it. The account can hold up to 100 sets. Add and edit users can assign a set only when they already hold every permission in it (permission sets).

  3. On Professional, open the user and edit permissions. Choose how to set access, then Start with a template or Start from scratch. Compare access for users needs Professional or Enterprise. Comparing sets is Enterprise only (manage user permissions). Saving a reusable set is the Enterprise control on the page after you add a user (add users). Until a set exists, copy one known-good user when the next person joins, then compare the two. Copy permissions to another user is a beta a Super Admin can opt the account into, from Actions, Manage permissions.

  4. Add the user and the seat. The add-users article requires Super Admin to create users: Settings, Users & Teams, Add users, then email, seat, permissions and team. Change a seat from the user's Actions menu or the Seats tab. Super Admin or Modify billing assigns seats. Read the access back after the set is on. The set does not open a tool the seat lacks. On Enterprise, a user import can include a permission set column (add users, seats).

  5. Restrict properties next. That screen is Enterprise and needs Super Admin.

  6. Wait, then test as that user. Updates can take up to five minutes. After that, the user logs out and back in, and on mobile they close the app and open it again. If a browser still shows the old access, HubSpot's check is a private window, then a cache clear (manage user permissions). Ask for one record they should see and one they should not.

When HubSpot adds a new permission to a set, people already on the set keep their access and the new permission turns on for them (manage user permissions). After a release, open the set and read the new rows.

Lock the properties that drive routing, forecasting and pay

Record scope is the wide gate. A few properties are the narrow one: owner, lead status, lifecycle stage, deal amount, close date, deal stage, and the territory or segment field routing reads. Who may change them decides whether routing and the forecast can be trusted. We cover how routing reads these fields in our lead routing guide. Lifecycle stage and lead status do different jobs, and we separate them in the lifecycle stage guide. We cover the hygiene under both in the data quality guide.

Property view and edit access needs Marketing, Sales, Service, Data, Content or Revenue Hub Enterprise, and a Super Admin. Open Settings, Data Management, Properties. Choose the object, hover the property, More, Manage access. Several properties can be set together, which overwrites what is already there. The choices are Private to super admins only, Allow everyone to view and edit, Allow everyone to view, and Assign to users and teams. Allow everyone to view leaves the value visible and limits editing to Super Admins. Assign to users and teams offers View and edit, View only, or No access. Access given to a nested team is also given to its parent. You cannot restrict another Super Admin (restrict property access, updated 9 Oct 2026).

HubSpot will not hide every field. You cannot restrict view of contact email, first name, last name or lifecycle stage. Company name, domain and lifecycle stage stay visible. On deals, deal name, pipeline, deal stage, close date, deal currency and last activity date stay visible. Lead name, pipeline, pipeline stage and last activity date stay visible. Ticket name, pipeline, ticket status, create date and close date stay visible. Record ID cannot have its edit access restricted. Some default properties have no Private to super admins only option, because they must stay visible (restrict property access).

Lifecycle stage, deal stage and close date are on that list, so hiding them is the wrong tool. Where Allow everyone to view is offered, that is the edit lock. Deal amount, owner and lead status are not on the list, so View only and No access are available. We leave owner visible, because Their team's is calculated from it. We restrict who can edit owner. An owner change moves the record across the team boundary and rewrites the HubSpot team property to the new owner's main team (teams).

The property article says this does not fully restrict access, and HubSpot does not recommend it as a security measure. Any user can still set a restricted property through the API, or while creating a record by hand. A UI lock stops a rep on the record. It does not stop an integration. If a field must not move, take Edit off the object, or withhold the write. The assets article's shorter property note says a limited property stays visible and points at the same edit message. Follow the property article when the two differ (properties, assets).

A manager who needs the forecast needs Reports access at view. Create and own, and the reporting Admin switch, are wider. Admin can create any report and overrides the other report settings. Enterprise can also limit which teams see a custom dashboard. Standard analytics views cannot be limited that way (permissions guide, assets). We cover how we lay the dashboards out in the dashboard guide.

Super Admin, integration users and AI connectors

Super Admin can do virtually anything in the account. A user with every toggle on, and without Super Admin, can still miss controls that sit outside the permissions panel. Paid Sales or Service features still need that seat. On a paid subscription the Super Admin must hold a Core, Sales or Service seat. Only a Super Admin can make another, from Users & Teams, Actions, Make Super Admin. When a task needs Super Admin, HubSpot recommends an existing Super Admin do it (permissions guide).

HubSpot does not publish a count. Only a Super Admin can create another, and deleting your own user is refused while you are the only one left (remove users). We keep a small named list, with more than one person on it, so a holiday does not freeze billing and user admin. RevOps gets Add and edit users, Add and edit teams, and Edit property settings. Modify billing stays with the person who owns the contract, because that permission buys and assigns paid seats.

An integration user is a login for a job. It gets the objects that job writes, Delete on None, Export off, and no App Marketplace access, which is the switch for installing apps. Give it a main team that matches the records it should see. A parent team is wider than the name on the screen. An extra team opens records and leaves the user out of routing and team reports, which is often the right shape for a service account (teams).

An assistant follows the same rule. The HubSpot remote MCP server (Model Context Protocol) runs as the user who authorises it, so that user is a dedicated login with a narrow set. We cover setup, limits and the audit check in the HubSpot MCP server guide. Work that must run with nobody at the keyboard belongs in HubSpot workflows or in n8n. Create being off on a human user does not stop a workflow from making records. The workflows permission, and the credential the automation uses, are the controls. When those rules have to hold across the CRM, enrichment and the automations, we cover the wider build on GTM engineering.

Removal has a private-app catch. Remove the user who created a private app, or remove their Super Admin permissions, and HubSpot says association calls fail with USER_DOES_NOT_HAVE_PERMISSIONS. The page's remedies are to recreate the app, rotate the token, or add the user back with the same permissions (remove users). Name an owner for the integration user before it creates anything.

A portal that already has years of one-off grants is worth a pass before the next hire. That review is the sort of work we do as a second opinion.

Keep it clean: offboarding and quarterly access reviews

Deactivate, then remove. Both work on all products and plans, and both need Super Admin. HubSpot Support cannot deactivate or remove a user. Deactivation can take up to five minutes, after which the person can no longer log in. The profile stays, so reporting history stays, and they remain assigned to their records. The paid seat stays attached and stops counting against the seat total. They drop out of conversations, assets and reports. Reactivating restores the previous access, including seats that were not unassigned (remove users, updated 13 Nov 2026).

Removal needs a deactivated user. The profile leaves the account, and you cannot restore it. Adding the email back later creates the user again, and HubSpot still treats it as the same user account. Reassign records they owned. Until you do, the owner shows as Deactivated/Removed plus the email. Assets they created stay, including pages, workflows, forms, reports, logged emails and notes. Scheduling pages they created are deleted. Sequences and templates remain available to others only if they were shared first.

Before deactivation, reassign assets, take them out of workflow filters, and deal with meetings. HubSpot cannot transfer the default meeting link. Ask them to turn scheduling pages off, or remove them after deactivation. On Enterprise someone can log in as them to do it. A round-robin page that still includes them keeps booking meetings in their name. The contact timeline does not show the meeting, and a workflow that fires on a meeting with that user stops firing. Take them off Account and Billing points of contact, or removal is blocked.

Two screens support the review. User permission history is on all products and plans and needs Super Admin: Users & Teams, Actions, Manage permissions, View user permission history. It shows the permission, whether it was added or removed, who changed it, and when. An Automated Change row is a system change. Export covers the last 90 days (permission history, updated 6 Nov 2026).

The audit log is separate. It is on Starter, Professional and Enterprise of Marketing, Sales, Service, Data and Content Hub, and that article requires Super Admin to view and export it. The permissions guide also lists an Audit log access switch, so confirm a Super Admin can open Settings, then Audit Logs, before you promise the log in a review. The log records actions a HubSpot user took. A form fill that no user made does not appear. Starter and Professional can filter the category to Login or Security Activity. Enterprise can filter further, including Approval, Content and Workflows. The same article's table marks CRM object actions, property updates, property value updates and workflows for Professional and Enterprise. On Professional we open the log and write down which categories it actually shows. We do not promise CRM field history on Starter from the category filter alone (audit log, updated 30 Oct 2026). A Super Admin can export security activity for the last year, including user and admin changes and deactivations.

We review access on a schedule, usually once a quarter, and again when a role changes. Each user still matches a set, each Super Admin is still named, and the integration users are still narrow. Permission history for the quarter shows no surprise Automated Change and no new permission a set turned on by itself. Owners who have left are reassigned, and we cover that work in the data governance guide. Associations are where that move goes wrong, and we walk through that check in the CRM audit guide.

Common HubSpot permission mistakes

Everyone is a Super Admin. A shortcut taken during implementation is never undone. Keep a named list, with more than one person on it, and let RevOps hold Add and edit users. When a task needs Super Admin, someone already on that list does the work.

Permissions live on each user, with no set. The second SDR starts as a copy of the first, until someone flips one extra switch. On Enterprise, give the role one set and assign it so the set replaces the individual grant. On Professional, keep one template user per role, and run Compare access before you treat the two users as the same.

Reps have All, with Edit. Amount, stage and owner move because the record allowed it. Use Their team's for view, Their for edit, and Delete on None, then add the property locks Enterprise allows. Test the result with a record from another team.

Teams do not match the territories. Their team's follows the team list, so a team that is not a territory shows the wrong book, and a parent team includes every team under it. Build the teams from the same list you use for routing, and put a manager on a parent only when that wider view is intentional. Use an extra team when someone needs the records and should stay out of rotation.

The integration user has no owner, or it is a person's Super Admin login. The writes have no name, and a departure takes the private app down with that person. Give the job a dedicated user, a set, a main team and Delete on None, and name a holder for the credential. Read the private-app note before you deactivate that user.

Nobody looks again. A set edited months ago still has the permissions HubSpot turned on by default, and people who have left can still log in. Run the quarterly pass, read permission history for the period, and deactivate the user on the day they leave. After that, confirm the login fails.

FAQ

Which HubSpot plan do I need for permission sets?

Enterprise. The hubs named on the article are Marketing, Sales, Service, Data, Content and Revenue Hub Enterprise. A Super Admin creates and edits sets, an account can hold up to 100, and assigning a set overrides that user's own permissions. A set can be assigned with no seat, and access is then the combination of the set and the seat's features (permission sets). The underlying permissions exist on all products and plans. Professional can use a role template, compare users, and assign presets. Saving the set is the Enterprise step (add users).

What is the difference between a seat and a permission?

A seat decides which tools open. A permission decides what the user can do with them. View-Only can look and log notes, and cannot edit or be a Super Admin. A Core, Sales, Service or Revenue seat opens that seat's tools. A permission left on does not open a tool the seat lacks, and a seat change does not by itself rewrite the toggles (seats).

Can I stop reps editing specific properties?

On Enterprise, a Super Admin can set Private to super admins only, Allow everyone to view, or access for specific users and teams. You cannot hide view of lifecycle stage, deal stage, close date, and the other properties on HubSpot's list. Those stay visible. The edit lock is the control where the screen offers it. Any user can still set a restricted property through the API or while creating a record, so HubSpot does not recommend this as a security measure (properties).

How many Super Admins should a HubSpot account have?

HubSpot does not publish a number. Only a Super Admin can create another, and you cannot delete your own user while you are the only Super Admin left (permissions guide, remove users). Our practice is a small named group, with more than one person, kept separate from the day-to-day revenue team.

Why are permission changes not showing for a user?

They can take up to five minutes. After that, the user logs out and back in. On mobile, close the app and open it again. If the browser still looks wrong, try a private window, and clear the cache if the private window is right. A limited asset can override the permission you just set, and a seat can keep a tool closed while the permission is on (manage user permissions, seats).

Can HubSpot Support change user permissions for me?

No. HubSpot states that Support cannot change user permissions (manage user permissions). Support also cannot deactivate or remove users. A Super Admin in the account makes the change, or grants Add and edit users to someone who already holds the permissions they will assign.

If you want the roles, the sets and the property locks decided before the next hire lands in the portal, we do that as part of CRM and RevOps.

Talk to us