> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-hold-policy-references-ga.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a HubSpot connector

> C1 provides identity governance and just-in-time provisioning for HubSpot. Integrate your HubSpot instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

## Capabilities

| Resource | Sync                                                          | Provision                                                     | Lifecycle actions |
| :------- | :------------------------------------------------------------ | :------------------------------------------------------------ | :---------------- |
| Accounts | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |                   |
| Teams    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                   |
| Roles\*  | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                   |
| Users    | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                   |

\*HubSpot roles are only supported on the free or higher versions of **Marketing Hub, Sales Hub, Service Hub,** and **Content Hub**. Role syncing and provisioning via this connector are not available when using any other HubSpot product or version.

## Provisioning

C1 can provision access in HubSpot using this connector. Provisioning requires the `settings.users.write` scope on the private app (see the credentials steps below) and that the connector runs with provisioning enabled (`BATON_PROVISIONING=true` when self-hosted).

| Operation                                          | Supported | Notes                                                                                                                     |
| :------------------------------------------------- | :-------- | :------------------------------------------------------------------------------------------------------------------------ |
| Grant / revoke a **Role**                          | Yes       | Assigns or clears the user's role. The **Super Admin** role cannot be assigned through the HubSpot API.                   |
| Grant a **Team** membership (primary or secondary) | Yes       | Adds the user to the team as a primary or secondary member.                                                               |
| Revoke a **primary Team** membership               | Yes       |                                                                                                                           |
| Revoke a **secondary Team** membership             | No        | The HubSpot API does not support removing a secondary team membership. Remove it manually in HubSpot.                     |
| Create a **User** account                          | Yes       | Invites the user to the HubSpot portal by email. No password is set — the user completes setup from the invitation email. |
| Delete a **User** account                          | Yes       | Removes the user from the HubSpot portal.                                                                                 |

<Note>
  HubSpot provides no API to re-enable a deactivated user. To restore access for a user who was deactivated in HubSpot, delete the account and re-invite it. This creates a new account and does not preserve the previous user's history.
</Note>

Deactivated HubSpot users continue to appear in C1 with their existing entitlement grants, because the account still exists in HubSpot. Enable **user status** syncing (see the configuration steps below) to have these users flagged as disabled in C1.

## Gather HubSpot credentials

Configuring the connector requires you to pass in credentials generated in HubSpot. Gather these credentials before you move on.

<Warning>
  A user with the **Super admin** role in HubSpot must perform this task.
</Warning>

### Create a private app and generate an access token

<Steps>
  <Step>
    Log into HubSpot and navigate **Settings** > **Private Apps**.
  </Step>

  <Step>
    Click **Create a private app**
  </Step>

  <Step>
    On the **Basic info** tab, enter a name (such as "C1") and description for the new app.
  </Step>

  <Step>
    On the **Scopes** tab, select the following scopes:

    In the **Settings** area:

    * `settings.users` - Read
    * `settings.users.teams` - Read

    In the **Standard** area:

    * `account-info.security.read` - Request
    * `integration-sync` - Request
    * `oauth` - Request
  </Step>

  <Step>
    **Optional.** If you want to use C1 to provision users (invite, deactivate) or manage team/role membership, add `settings.users.write`.
  </Step>

  <Step>
    **Optional.** To sync user status, search for and add the `crm.objects.users.read` scope to the app.
  </Step>

  <Step>
    Click **Create app** and confirm your action.
  </Step>

  <Step>
    The new private app's token is shown. Carefully copy and save the token.
  </Step>
</Steps>

**Done.** Next, move on to the connector configuration instructions.

## Configure the HubSpot connector

<Warning>
  To complete this task, you'll need:

  * The **Connector Administrator** or **Super Administrator** role in C1
  * Access to the set of HubSpot credentials generated by following the instructions above
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **HubSpot** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new HubSpot connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Paste the private app access token into the **Access Token** field.
      </Step>

      <Step>
        **Optional**. If you want to sync user statuses from Hubspot, click to **Enable user status**.

        This option requires the `crm.objects.users.read` scope, so make sure you've added it to your private app before you proceed.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your HubSpot connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Hubspot connector, hosted and run in your own environment.**

    When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

    ### Resources

    * [GitHub repository](https://github.com/conductorone/baton-hubspot): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new HubSpot connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new HubSpot connector:

        * Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)

        * Add the connector to a managed app (select from the list of existing managed apps)

        * Create a new managed app
      </Step>

      <Step>
        Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

        If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your HubSpot connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-hubspot-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-hubspot-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>
      
      # HubSpot credentials
      BATON_TOKEN: <HubSpot private access token>

      # Optional: include if you want to sync user statuses (requires the crm.objects.users.read scope on the private app)
      BATON_USER_STATUS: "true"

      # Optional: include if you want C1 to provision access using this connector
      BATON_PROVISIONING: "true"
    ```

    See the connector's README or run `--help` to see all available configuration flags and environment variables.

    #### Deployment configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-hubspot.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-hubspot
      labels:
        app: baton-hubspot
    spec:
      selector:
        matchLabels:
          app: baton-hubspot
      template:
        metadata:
          labels:
            app: baton-hubspot
            baton: "true"
            baton-app: hubspot
        spec:
          containers:
          - name: baton-hubspot
            image: public.ecr.aws/conductorone/baton-hubspot:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-hubspot
            envFrom:
            - secretRef:
                name: baton-hubspot-secrets
    ```

    ### Step 3: Deploy the connector

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the HubSpot connector to. HubSpot data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

    **Done.** Your HubSpot connector is now pulling access data into C1.
  </Tab>
</Tabs>