On this page
What HubSpot supports natively
| Access route | How it works | Notes |
|---|---|---|
| Partner access | A partner admin sends an access link from Client Access Manager; the client’s approval adds the partner as a Partner Admin | The partner can change a partner employee’s permissions to a HubSpot default permission set; billing access is granted separately by a Super Admin |
| Partner Seat | Partners on seats-based pricing can use a free Partner Seat in client accounts | Not available on legacy-pricing accounts |
| User with a permission set | You invite the auditor as a user | Choose view access for the areas in scope |
| Connected app | An audit tool connects through HubSpot’s app authorization | The app’s overview page lists the features it’s authorized for |
| Super Admin-only areas | Audit logs, security activity export | Needed only if these are in scope |
How to grant audit access safely
- Write the scope first. List the hubs and areas the audit covers.
- Pick the route. Partner access for agencies, a user for freelancers, app authorization for a tool.
- Grant the least access that works. View access to what’s in scope; Super Admin only for audit logs and security exports.
- Agree that nothing changes during the audit. Say so in writing.
- Record what you granted, with dates.
- 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
- Manage partner employee access to client accounts (HubSpot Knowledge Base)
- View and export account activity history (HubSpot Knowledge Base)
- Manage your connected apps (HubSpot Knowledge Base)
- Connecting your first portal (Jetstack AI documentation)
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