---
updatedAt: 2026-08-05T10:15:40.000Z
agentTools:
  projectIndex: https://docs.axonius.com/llms.txt
---

# Halo - Link Device to User

**Halo - Link Device to User** links a Halo device asset to a user account for:

* Assets returned by the selected query or assets selected on the relevant asset page.

See [Creating Enforcement Sets](/docs/create-ec-set) to learn more about adding Enforcement Actions to Enforcement Sets.

<Accordion title="When accessing an enforcement action using the API, you must use the backend form of field names. " icon="fa-info-circle">
  Use the [Syntax Helper](/docs/using-the-syntax-helper) to find the correct name. In the enforcement action, enable **Configure Dynamic Values** and select **Syntax Helper**.


  <Image src="https://raw.githubusercontent.com/Axonius/ax-docs-pub/refs/heads/main/img/action_center/SyntaxHelperForAPIECs.png" width="550px" />

</Accordion>

<Callout icon="📘" theme="info">
  ### Note

  - Not all asset types are supported for all Enforcement Actions.
  - See Actions supported for [Activity Logs, Adapters Fetch History, and Asset Investigation modules](/docs/creating-queries-filters#using-activity-log-adapter-fetch-history-asset-investigation-and-findings-queries-in-enforcement-actions).
  - See Actions supported for [Aggregated Security Findings](https://docs.axonius.com/docs/vulnerabilities#using-aggregated-security-findings-queries-in-enforcement-actions).
  - See Actions supported for [Software](software#using-software-queries-in-enforcement-actions).
</Callout>

## Required Fields

These fields must be configured to run the Enforcement Action.

* **Action name** - The name of this Enforcement Action. The system sets a default name. You can change the name.
* **Configure Dynamic Values** *(optional)* - Toggle on to enter a Dynamic Value statement. See [Creating Enforcement Action Dynamic Value Statements](https://docs.axonius.com/docs/config-ec-conditions) to learn more about Dynamic Value statement syntax.

- **Use stored credentials from the Halo adapter** - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
  * When you select this option, the **Select Adapter Connection** drop-down becomes available. Select the adapter connection to use for this Enforcement Action.

<Callout icon="📘" theme="info">
  ### Note

  If you do not select this option, you must provide the Halo adapter connection settings below.
</Callout>

* **Compute Node**  - The Axonius node to use when connecting to the specified host. For more details, see [Working with Axonius Compute Nodes](https://docs.axonius.com/docs/connecting-additional-axonius-nodes).
* **Halo User ID** - Populated automatically via "Configure Dynamic Values" → Relation → Users → Latest last used user → Aggregated → Halo adapter → Halo ID.

<Callout icon="📘" theme="info">
  ### Note

  This field is automatically populated using Configure Dynamic Values. Navigate to the device's related user, select the latest user, and map the Halo User ID field from the Halo adapter data.
</Callout>

## Additional Fields

This Enforcement Action does not have additional optional fields.

<Callout icon="💡" theme="warn">
  ## Connection and Credentials

When **Use stored credentials from the adapter** is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.

  - **Host Name or IP Address** - Base domain for the Halo API, should contain a prefix of http\:// or https\://. Do not add any specific endpoints after the domain. Example of a valid domain: `https://www.halo.com/`
  - **Client ID** - Client ID for OAuth authentication with the Halo API.
  - **Client Secret** - Client Secret for OAuth authentication with the Halo API.
  - **Tenant** - Tenant identifier (only used for Hosted Solution).
  - **Verify SS&#x4C;_&#x20;(Optional)_**_&#x20;(default: enabled)&#x20;_- Selects whether to verify the SSL certificate of the server against the CA database inside of Axonius.  For more details, see [SSL Trust & CA Settings](/docs/certificate-settings#ssl-trust-ca-settings). This setting is enabled by default on all new adapter settings. If you need to disable SSL verification, make sure you disable this setting._)_&#x20;
  - **HTTPS Proxy** *(optional)* - Connect the adapter to a proxy instead of directly connecting it to the domain.
  - **HTTPS Proxy Password** *(optional)* - The password to use when connecting to the server using the **HTTPS Proxy**.
  - **HTTPS Proxy User Name** _(optional)_ - The user name to use when connecting to the server using the  **HTTPS Proxy**.
  - **Gateway Name** -  Select the Gateway through which to connect to perform the action.
</Callout>

## APIs

Axonius uses the Halo API - POST `/api/Asset`

## Required Ports

Axonius must be able to communicate via the following ports:

* TCP port 80/443

## Required Permissions

The stored credentials, or those provided in [Connection and Credentials](#connection-and-credentials), must have the following permission(s) to perform this Enforcement Action:

* A registered OAuth application in Halo with Client ID and Client Secret
* The API user must have permissions to update asset records and link users to assets

**Note:** The exact permission names should be confirmed with your Halo administrator or Halo support, as the API documentation is not publicly available.

To learn more about Enforcement Actions, see [Enforcement Actions](/docs/enforcement-actions).

## Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact [Axonius Support](mailto:support@axonius.com) if you have a version that is not listed and it is not functioning as expected.

| Version                          | Supported | Notes                    |
| -------------------------------- | --------- | ------------------------ |
| Halo Service Desk (All Versions) | ✅         | Tested with Halo API     |
| Halo ITSM                        | ✅         | Compatible with Halo API |
| Halo PSA                         | ✅         | Compatible with Halo API |