HubSpot scopes we request

When you connect HubSpot, you approve a fixed set of permissions, called scopes. DavenportAI requests only what it needs to read your lists, read and update contacts and companies, and create its own properties.

The scopes

Scope	Why we need it
oauth	Required by HubSpot for every app that connects with OAuth.
crm.lists.read	Show your lists in the job picker and read which records are in a list.
crm.objects.contacts.read	Read the contact fields a job uses as input, such as name, email and company.
crm.objects.contacts.write	Write results back to your contacts.
crm.schemas.contacts.read	Check which contact properties already exist before creating any.
crm.schemas.contacts.write	Create the DavenportAI property group and its contact properties.
crm.objects.companies.read	Read the company fields a job uses as input.
crm.objects.companies.write	Write results back to your companies.
crm.schemas.companies.read	Check which company properties already exist before creating any.
crm.schemas.companies.write	Create the DavenportAI property group and its company properties.

What we do not ask for

DavenportAI has no access to deals, tickets, emails, conversations, marketing emails, forms, files, users or settings in your portal.

How your connection is stored

HubSpot gives DavenportAI an access token when you connect. Tokens are encrypted at rest and are only decrypted by the service that runs your jobs. You can disconnect at any time by uninstalling DavenportAI in your HubSpot settings under Connected apps.