Skip to main content
Use these connections to discover company names and identifiers, then explicitly link them to Alignr clients. They do not copy documentation, passwords or assets, supply assessment facts, or execute remediation.

​
Connect one source, then verify one client

  1. Open Integrations and add the intended product. Give the connection a name that identifies its account, controller or region.
  2. Enter the fields for that product below. Obtain credentials through the vendor administrator responsible for the intended account; a field list does not grant API entitlement or permissions.
  3. Review the saved connection outcome, then use Clients & sites to discover and explicitly assign the correct source records. Compare identifiers as well as names.
  4. For evidence sources, use Sync now, inspect Sync history, and check one client’s source and observation time. Directory sources instead use Import clients and Refresh client records.
  5. Compare the available observations with the control’s requirements before running checks.
Checkpoint: one known source record maps to the intended client and the expected observations are present. A successful credential save alone is not a completed assessment. The tables show the current Alignr form. “Required” means the form requires a value; optional fields can still be necessary for your account or connection mode. Keep secrets in the credential fields.

​
Choose your product

Choose the correct region: us, eu or au (default us). The key must be able to read the intended Organizations. Alignr reads company names and IDs only through this directory connector.Map: Each IT Glue Organization ID.Available observations: None. This is a client-directory connection.
Use the Hudu instance URL and an API key permitted to read the intended companies. This connector imports company names and IDs only; it does not migrate Hudu documentation or secrets.Map: Each Hudu company ID.Available observations: None. This is a client-directory connection.Use the vendor’s current instructions for credential preparation: Hudu REST API key setup.

​
If the expected evidence is missing

Check the account or region, the discovered source ID and the completed collection outcome. Then compare the list above with the predicate reference. A supported product can still lack the particular observation your control needs. Do not turn an absent observation into a passing value. Maintain or reconnect a source, or trace a coverage gap.