What can an AI agent do with
Full ticket access (legacy)?
An older permission to view and manage support tickets. HubSpot recommends newer, narrower ticket permissions instead.
How to spot it
On a HubSpot connection or settings screen, this is tickets.
With it, an agent can
- See support tickets
- Manage ticket data
It cannot, on its own
- See or edit Sensitive Data fields on tickets (separate permissions)
What a bad day looks like
The agent closes or changes open customer tickets by mistake, so real problems go unanswered.
Set it up safer
- Ask for crm.objects.tickets.read if it only needs to read tickets
- Ask for crm.objects.tickets.write only if it must change them
Ask the company selling the agent
- Why do you use the legacy tickets permission?
- Will the agent close or delete tickets on its own?
Source
Checked against HubSpot documentation on 2026-09-28. All HubSpot permissions →
Thinking about a specific agent?
Tell us what it connects to, what it is allowed to do and who approves its work. You get a plain-language label of what it can touch and what to ask the seller. It takes a couple of minutes, and your answers stay in your browser unless you choose to post a test job.
Or have a person go through the AI apps on up to 3 of your business services with you and get a written report, for $249.
This page explains what a permission allows. It does not describe, test or rate any product. Permission details are summarized in our own words from the provider's documentation, linked on the page; providers change their documentation, so check the source before you rely on a detail.