Choose a HubSpot seat by the work a person must do, not by their job title. A reader may only need a View-Only Seat. A user who builds CRM, marketing or operations assets usually needs a Core Seat. Sales, service and revenue specialists need the matching seat when they use the paid Professional or Enterprise tools.
The detail many teams miss: Sales, Service and Revenue Seats include Core access. You do not buy a separate Core Seat on top. Seats unlock types of features; permissions decide what each user may view, create, edit or delete.
Start with the table below, then confirm the exact tools each person uses. A title such as “sales manager” is not enough: one manager may only read forecasts, while another builds sequences and coaches reps in Sales Hub.
| Role or task | Likely seat | Why |
|---|---|---|
| Executive, board member or finance user who only reads records and reports | View-Only Seat | They can inspect information but cannot edit or use several active tools. |
| Marketing, operations, CRM or content user who builds and edits | Core Seat | They need the core features included in the account's subscription. |
| Sales rep or manager using Sales Hub Professional or Enterprise tools | Sales Seat | It unlocks the full Sales Hub feature set and includes Core access. |
| Support or customer success user working in Service Hub Professional or Enterprise | Service Seat | It unlocks the full Service Hub feature set and includes Core access. |
| User creating or editing quotes and working in Revenue Hub Professional or Enterprise | Revenue Seat | It unlocks the full Revenue Hub feature set and includes Core access. |
| Eligible HubSpot Solutions Partner employee working in a client account | Partner Seat | It gives eligible partner employees free access to client features. |
| Developer who only needs HubSpot's developer platform | Developer Seat | It is free and isolated from ordinary CRM access. |
If you are comparing packages as well as seats, read the HubSpot Customer Platform pricing guide. For a Norwegian seat comparison, see Core Seat, Sales Seat and Service Seat explained.
A HubSpot seat is the type of product access assigned to a user. It determines which class of HubSpot features that person can access. It does not decide every action they may take: user permissions control the finer rights inside that access.
This distinction prevents two expensive mistakes. You should not buy a specialist seat to solve a permissions problem, and you should not grant broad permissions just because someone has a paid seat.
Seat design is one part of a wider HubSpot setup: ownership, teams, data, permissions and process still have to work together.
The four paid seat types match different kinds of work. Sales, Service and Revenue Seats include Core access, so assign one specialist seat to a user who needs that specialist toolset.
A Core Seat gives access to the core features available in your subscription. It is commonly the right fit for people who create or edit CRM data, lists, forms, content, reports, automation and account configuration.
Typical users include marketers, operations specialists, CRM owners, content producers and administrators. Their permissions should still be limited to the work they are responsible for.
A Sales Seat gives a user the full Sales Hub Professional or Enterprise feature set available in the account. It is intended for salespeople and managers who actively use paid sales tools, not everyone who happens to view a deal.
For package context, see the guide to HubSpot Sales Hub pricing.
A Service Seat gives a user the full Service Hub Professional or Enterprise feature set available in the account. It suits support and customer success teams that actively run service processes in HubSpot.
A Revenue Seat gives a user the full Revenue Hub Professional or Enterprise feature set available in the account. A Core user can view quotes in those editions, but creating or editing quotes requires a Revenue Seat.
Revenue Hub was previously called Commerce Hub. Use the current name when planning access and compare the wider package in the Revenue Hub pricing guide.
A View-Only Seat is enough when a person genuinely only needs to inspect HubSpot data and assets. It is often suitable for executives, board members, finance users and occasional stakeholders who review dashboards, records or progress.
View-Only is not a lighter editing seat. These users cannot create changes or save edits. HubSpot also restricts several active tasks, including logging or tracking emails and creating contacts from emails, and a View-Only user cannot be a Super Admin.
Ask one concrete question before assigning it: “What must this person change, send, create or configure?” If the honest answer is “nothing”, test View-Only first.
Partner and Developer Seats solve narrower access problems and can prevent unnecessary paid-seat assignments.
HubSpot provides a free Partner Seat to eligible employees of Solutions Partner and provider organisations. It is designed for partner work in client accounts. Do not give an external partner a paid client seat automatically; first check whether the person qualifies and whether their partner access is correctly configured.
A free Developer Seat gives access to HubSpot's developer platform without ordinary CRM access. It cannot be combined with another seat or the Super Admin role. If an existing paid-seat user also develops, HubSpot instead allows developer tools access through permissions.
A seat answers “which product features can this user access?” Permissions answer “what can this user view, create, edit or delete inside that access?” You need both layers to match the person's responsibilities.
Super Admin is not a shortcut around seat requirements. A Super Admin still needs the relevant Sales or Service Seat to use paid Sales Hub or Service Hub features. On a paid account, a Super Admin also needs a paid seat rather than View-Only.
Changing a seat does not automatically rebuild the user's permissions. Review both after every role change. HubSpot notes that permission updates can take a few minutes and may require the user to sign out and back in.
Audit seats before renewal and whenever people, packages or responsibilities change. The purpose is not to remove useful access. It is to match every recurring cost to a current task.
Accounts created before 5 March 2024 may still use HubSpot's legacy seat model until migrated. Confirm which model your account uses before applying this framework.
A user usually needs a Core Seat when they create, edit or configure the core CRM, marketing, content, operations or reporting features included in the account. Someone who only reads records and reports may be able to use View-Only instead.
No separate Core Seat is required. HubSpot's Sales, Service and Revenue Seats include Core access. Assign the specialist seat that matches the paid Professional or Enterprise tools the person actually uses.
No. Super Admin controls permissions but does not unlock paid Sales Hub or Service Hub features. A Super Admin on a paid account must also have a paid seat rather than a View-Only Seat.
Not necessarily. Unassigning separates the seat from the user, but the subscription can still contain an unassigned paid seat. Check the account's seat quantity, minimum commitment and contract terms before renewal.
Accounts created before 5 March 2024 may remain on HubSpot's legacy pricing model until migrated. Use the seat options and billing rules shown in your own account, and confirm changes with HubSpot before altering a renewal.
A useful seat review covers users, permissions, Sales/Service/Revenue workflows and the subscription—not just the user list. We can map the work, remove ambiguous access and leave you with a rule your team can maintain.