Use one FullHunt organization per customer or operational boundary. The durable integration key is the FullHunt organization ID, not its display name.

Requirements

  • Enterprise API access
  • Permission to create organizations and add assets
  • Authorized domains and public IP ranges for the tenant
  • Python 3.10 or later with requests

Onboarding contract

Organization creation is not an idempotent API operation. The script checks for an exact existing name before creating one and writes a recovery journal immediately after creation.

Run onboarding

Use real authorized assets when running the script. The .example domains and documentation IP range above only show the expected input format.
onboard_enterprise_tenant.py

Production controls

  • Keep the authorization reference in your internal journal. Do not place contracts or secrets in organization descriptions.
  • Treat 409 Conflict while adding scope as an ownership or tenancy conflict requiring review.
  • Do not automatically delete an organization to roll back partial onboarding. Organization deletion cascades to associated account data.
  • Apply the org filter to alerts, vulnerabilities, and entities. Keep separate cursors and state files for each tenant.
  • Test offboarding, reassignment, and failed partial onboarding before operating at scale.
The initial counts prove that the API calls completed. They do not prove asset discovery is finished. Store a dated inventory snapshot before evaluating later drift.