Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 37 ยท Getting Started

HubSpot Users, Teams and Permissions

Invite users, assign seats, organize teams and set permissions in HubSpot so people can do their jobs without seeing or changing more than they should.

A CRM holds personal data, deal values and private notes, so who can see and change what matters. HubSpot controls this with users, teams and permission sets. Getting them right early prevents both accidents (someone deleting a pipeline) and leaks (a contractor reading every deal).

Users and seats

A user is a person who logs in. In Settings > Users & Teams an admin can invite people by email, then assign:

  • Permissions. What the user may view, create, edit, delete, export or administer.
  • Seats. Which paid tools the user can use (for example a Sales seat gives access to Sales Hub tools such as sequences). A user with no paid seat can still use free tools.
  • Teams. Groups the user belongs to.

Roles you will see often:

  • Super Admin. Full control, including billing and account-wide settings. Keep this to a small, named group (two or three people), so there is never a single point of failure and never a crowd of owners.
  • Standard users. Everyone else, with permissions chosen from a template or set manually.

Create at least two Super Admins so you are not locked out when one leaves. Never share a login: shared accounts destroy audit trails and make permissions meaningless.

Teams

A team groups users, usually by function or region: "SDR team", "Enterprise EMEA", "Support Tier 1". Teams are used for:

  • Record visibility. Permission rules can say "users see only records owned by their team" (in editions that offer this).
  • Assignment. Round-robin and rotation tools assign leads to a team's members.
  • Reporting. Dashboards and reports can filter by team.

In Enterprise editions teams can be hierarchical: a parent team (like "EMEA") contains child teams (like "EMEA Sales", "EMEA Support"), and a manager can see their team's records.

Permissions

Permissions fall into groups:

Group Examples of what it controls
CRM View, edit, create, delete, export and merge records of each object; whether a user sees all records, only their own, or their team's.
Marketing Create and publish email, forms, landing pages; manage lists, campaigns; edit ads and social accounts.
Sales Use sequences, templates, quotes, call recordings; manage meetings.
Service Manage tickets, inbox, knowledge base, feedback surveys.
Reporting Create dashboards, share them, create custom reports.
Account Manage users, billing, properties, integrations, tracking code.

Permission sets (templates) are saved bundles you assign to many users. Use them instead of editing each user.

The principle of least privilege

Give each person the smallest set of permissions that lets them do their work. Practical rules:

  1. Only admins create or delete properties, pipelines and workflows.
  2. Many teams get "export" turned off; exports are the most common route for data leaving the company.
  3. Contractors get access limited by team or owner, with an end date on the calendar.
  4. Reps can edit their own deals but not delete them.

Enterprise editions add finer controls such as field-level permissions (restricting who can view or edit a specific property) and business units for separate brands.

Record ownership

Contacts, companies, deals and tickets can have a record owner, usually the one user accountable. Ownership drives:

  • "My contacts", "My deals" views and notifications.
  • Who gets a task when a workflow says "create a task for the owner".
  • Visibility when permissions say "owned records only".

A few best practices: always set an owner on deals, set an owner on new leads automatically through workflows or lead rotation, and reassign the records of a person who leaves before you remove them.

Modeling permissions (stand-in)

The program below is a stand-in that models the idea of permission sets. It is not HubSpot's engine, but it shows why "least privilege plus ownership" behaves the way it does.

JS Stand-in: permission sets and ownership

Press Run (or Ctrl + Enter) to see the console output here.

No output.

JS Stand-in: audit for risky settings

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Run a similar review by hand every quarter: list users, last login, seats and export rights, and remove what is no longer needed.

Security extras

  • Two-factor authentication. Require it for all users in account security settings.
  • Single sign-on (SSO). Higher editions let you log in through your identity provider.
  • Activity logs. Admins can review login history and security activity to spot misuse.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the principle of least privilege?

    Limiting access to what is needed reduces accidents and data leaks.
  2. 2. What is a permission set used for?

    Permission sets act as reusable templates so you do not configure each user by hand.
  3. 3. Why should you reassign records before removing a departing user?

    Ownership drives views, notifications and task assignment, so reassign first.
  4. 4. Why have at least two Super Admins?

    A single admin is a single point of failure; two or three named admins give resilience without a crowd of owners.

Summary

  • Users log in, hold permissions and seats, and belong to teams.
  • Teams drive visibility, assignment and reporting.
  • Use permission sets and the least-privilege principle; restrict exports.
  • Keep two or three Super Admins, require 2FA and review users regularly.

Next: CRM objects and records