Skip to content
Book a build

What access is needed to audit my HubSpot portal?

The access needed to audit a HubSpot portal depends on scope. A partner gets in through HubSpot's Client Access Manager, which the client approves; an employee gets a user with the right permission set; an audit tool connects as an app. Some areas, such as audit logs, need Super Admin. Grant the least access that covers the scope, and remove it when the audit ends.

On this page

What HubSpot supports natively

Access routeHow it worksNotes
Partner accessA partner admin sends an access link from Client Access Manager; the client’s approval adds the partner as a Partner AdminThe partner can change a partner employee’s permissions to a HubSpot default permission set; billing access is granted separately by a Super Admin
Partner SeatPartners on seats-based pricing can use a free Partner Seat in client accountsNot available on legacy-pricing accounts
User with a permission setYou invite the auditor as a userChoose view access for the areas in scope
Connected appAn audit tool connects through HubSpot’s app authorizationThe app’s overview page lists the features it’s authorized for
Super Admin-only areasAudit logs, security activity exportNeeded only if these are in scope

How to grant audit access safely

  1. Write the scope first. List the hubs and areas the audit covers.
  2. Pick the route. Partner access for agencies, a user for freelancers, app authorization for a tool.
  3. Grant the least access that works. View access to what’s in scope; Super Admin only for audit logs and security exports.
  4. Agree that nothing changes during the audit. Say so in writing.
  5. Record what you granted, with dates.
  6. Remove it afterwards. Deactivate the user, adjust partner permissions or disconnect the app, and check the audit log for activity during the audit.

Common mistakes

  • Making every auditor a Super Admin by default.
  • Forgetting to remove access when the engagement ends.
  • Connecting an app without reading what it’s authorized for.

When it’s worth a second look

If an auditor asks for Super Admin on day one, ask which areas need it. Audit logs and security exports do; reviewing workflows, pipelines and properties usually doesn’t. If a tool asks for broad permissions, ask the vendor what its audit reads and whether any other feature uses the same connection. A clear answer is a good sign; a vague one is a reason to wait.

Where Jetstack AI fits

Jetstack AI connects to a portal through HubSpot OAuth, and the Portal Audit only reads your portal: it doesn’t create, edit or delete anything. As with any app, review the permissions HubSpot shows when you connect. Some areas need the Chrome extension, and the report shows what couldn’t be collected. See connecting your first portal.

Sources

Checked October 29, 2026. HubSpot changes its products often; tell us at team@jetstack.ai if something here is out of date.

Portal audits

See what needs work before you change it.

A read-only Portal Audit and Workflow Audit score the portal, trace dependencies and turn findings into a branded report.

Explore Portal Audit

Portal audits

Related questions.

What access is needed to audit my HubSpot portal?

The access needed to audit a HubSpot portal depends on scope. A partner gets in through HubSpot's Client Access Manager, which the client approves; an employee gets a user with the right permission set; an audit tool connects as an app. Some areas, such as audit logs, need Super Admin. Grant the least access that covers the scope, and remove it when the audit ends.

Does an auditor need Super Admin?

Only for Super Admin areas, such as audit logs and some security exports. For the rest, a permission set with view access to the areas in scope is enough. If you do grant Super Admin, remove it when the audit ends.

How do I know what an app can access?

Each connected app's overview page in Settings > Integrations > Connected Apps shows the features it's authorized for. Check it before and after the audit.