<!--
  Translated by the docs agent from content-src/es/integrations/hubspot/03-en-hubspot-crear-la-aplicacion-privada-y-los-permisos.md
  (source_hash 7d1dd349d8e9). If that Spanish source_hash changes, re-check this translation.
-->

**Requirements:** a HubSpot account with permission to create private apps (section 2).

1. Log into your **HubSpot** account and go to **Settings → Integrations → Private Apps**.
2. Press **Create a private app**. Give it a recognizable name — for example your own business's name, never a generic one like "test".
3. Go to the **Scopes** tab and check these five permissions — the minimum the connector needs, not one more:

| Scope | What the connector uses it for |
| --- | --- |
| `crm.objects.contacts.read` | Search and read existing contacts. |
| `crm.objects.contacts.write` | Create or update a contact ("lead → contact" action, section 5). |
| `crm.objects.deals.read` | Search existing deals. |
| `crm.objects.deals.write` | Create a deal or change its stage ("stage → deal" action, section 5). |
| `crm.objects.owners.read` | Read the owners (HubSpot users) of a contact or deal. |

1. Save the app. HubSpot shows the **access token**, in the `pat-eu1-…` format — copy it before closing the window: for security, HubSpot only shows it in full this first time (afterwards you can reveal it again from the app's own **Auth** tab if you need it again).

> **Warning — Verified against the official documentation — a name that may vary**
>
> The path **Settings → Integrations → Private Apps** above is the one this guide uses because it's the one Platform's own connection form describes. When reviewing HubSpot's official documentation for this manual (`developers.hubspot.com/docs/api/private-apps` and `developers.hubspot.com/docs/guides/apps/private-apps/overview`, consulted on September 5, 2026), HubSpot today calls this same mechanism **"Legacy private apps"** and places it under the **Development → Legacy apps → Create legacy app → Private** menu of its developer portal. HubSpot keeps the mechanism working — a private app token still works the same — but it may have renamed or moved the menu in your account depending on when it was created. If you don't find "Private Apps" where step 1 says, look for "Legacy apps" instead; this note will be removed once the capture session confirms the exact path a new admin sees today.