--- name: halo-sites description: Find HaloITSM customers and Sites, and plan or troubleshoot location creation, imports, moves, site contacts, permissions, defaults and related users or assets. --- # HaloITSM customers, sites and users Follow the [operating contract](../../references/operating-contract.md). Reply in the user's language and preserve verified Halo setting names. ## Identify the target record - A Halo **Site** represents a customer location. Find it in **Customers > [customer] > Sites & Users**, select the Sites view, and check active and inactive records. For a self-service website, use [halo-portal-catalogue](../halo-portal-catalogue/SKILL.md). [Introduction to HaloITSM/ESM](https://www.usehalo.com/guides/2434) · [Customer, Site and User Records](https://www.usehalo.com/guides/878) - Establish the tenant, build, environment, exact parent customer and authoritative location identifier. Confirm which system owns customer, site, address and user updates. If display names collide, resolve the exact parent and matching record before making a change. - Record the site's intended name, address or contact details if needed, users, assets, routing expectations, import or integration mapping, and applicable access. Determine which fields and defaults the current tenant actually exposes. [Customer, Site and User Records](https://www.usehalo.com/guides/878) - Inventory existing mappings and defaults. A site change can affect portal logging, site contact rights, notifications, reporting and integration matches. Treat configuration assumptions as tests when no tenant evidence exists. ## Resolve a customer or location in a connected tenant 1. Use a supplied customer or Site ID for an exact lookup. With a name, search the customer first, then narrow the Site lookup by parent if supported. When the connection only offers text search, use returned customer and Site IDs to confirm the relationship. Compare candidate names under the intended parent and ask for a discriminator if ambiguity remains. 2. Return the matched customer, Site and verified record link when available. Add only the contact, user or asset information needed for the task. Restricted records, inactive Sites and partial search pages can hide duplicates. Verify those cases in the authorised admin view before using the result as an import or create decision. 3. When a user reports misrouting, compare the ticket's recorded Site with the requester's Site and the creation channel. Use that comparison to decide whether to inspect the requester mapping, portal setting, ticket rule or connector. [Ticket triage](../halo-tickets/SKILL.md) · [Portal catalogue](../halo-portal-catalogue/SKILL.md) ## Create or update a single site 1. In the customer record, open **Sites & Users**, switch to Sites, and use **New** to create the site. For an update, open the matched existing site. Record the resulting site ID and parent customer. Check the form's required fields and document any intentionally inherited values. [Customer, Site and User Records](https://www.usehalo.com/guides/878) 2. Associate users or assets only when included in the request. Compare existing assignment and integration mapping before moving either. Decide how historical tickets should remain associated and validate the effect of any move on new tickets. 3. Use the site's **Site Contacts** tab to add the intended contact and choose a contact type. Review the type under **Configuration > Users > Site Contact Types**. Verify effective ticket visibility, logging on behalf of users and recipient rules. Halo documents managing site contacts from the user profile as of v2.246. [Site Contacts](https://www.usehalo.com/guides/2506) 4. Create a test request as an affected end user and check the selected site, user and routing. Exercise agent, portal and integration channels that use site information. Check for unexpected recipient, visibility and access changes. ## Plan a bulk import 1. Obtain the current template from the target build. The vendor guide places the customer and site import under **Configuration > Users > General Settings > Import Customers & Sites**. Use the downloaded headers and verify the UI's chosen matching identifier for updates. Halo's site import guide documents `SF`-prefixed column headers for custom site fields. [Client, Sites & Users Import](https://www.usehalo.com/it/guides/2850) · [Importing Data](https://www.usehalo.com/guides/866) 2. Prepare a staging table with one agreed business key per customer and site. Resolve duplicates and conflicting parent references, including inactive sites. Normalize names and address data for review while preserving original values for reconciliation. Keep the authoritative keys and explicit blank-value policy. 3. Produce a preview with create, update, unchanged and conflict counts. Exclude unresolved rows from the import. If a source row could update more than one record, require a unique match before including it. 4. Import customers and sites before the dependent users. Pilot with representative records and inspect the import result, then query or export the resulting records to reconcile row counts and IDs. Where identity or asset sync also controls the location, verify that the next sync preserves the intended association. [Creating Users](https://www.usehalo.com/guides/2678?Use-Case=ITSM) 5. On partial failure, reconcile the successful rows and repair the rejected rows. Re-run only the reconciled subset unless the matching and update behaviour has been proven safe. Save the approved input, pre-change mapping, result summary and corrective actions without personal information in shared notes. ## Diagnose common failures | Symptom | Evidence to inspect | | --- | --- | | Site already exists after an import | Parent key, duplicate/inactive matches, selected import identifier and prior successful rows. | | New ticket lands in the default site | Requester record, ticket channel and portal site-selection settings, and the connector's mapping. | | Contact can see too much | Site Contact Type access level, each site assignment and end-user permissions. | | Contacts do not receive notices | Contact type and subscription or trigger, notification recipient criteria, correct site on the test ticket. | | A directory sync reverses a move | Authoritative directory mapping, match key and synchronization log from the most recent run. | | A Site is confused with a portal | Confirm whether the requested outcome is record ownership, a portal URL, branding, service eligibility or a SharePoint integration mapping. | ## Worked example for adding a branch to an existing customer For the illustrative customer Northwind Research, create the Aarhus branch using the agreed key `LOC-AAR-01` in the organisation's chosen matching field. First confirm that the customer and key resolve uniquely and that no inactive Aarhus site already exists. Use the current tenant's form to create the record. Record its returned ID, assign only the approved contact, and verify a test user's submitted ticket lands under Northwind Research and Aarhus. Where the site is managed by an upstream directory or asset source, add the mapping before enabling that sync for the branch. | Acceptance case | Expected evidence | | --- | --- | | Approved parent and unique site | The site is listed under the correct customer and the recorded ID matches the result. | | Similar name or inactive match | The intended record is resolved explicitly before a create or update. | | Unrelated user or other customer | No new visibility of branch tickets or contact details. | | Site contact | Only agreed site-scoped logging, visibility and notifications. | | Repeat import or sync | No duplicate site and no unexpected reversal of the intended mapping. | | Failed import row | Successes and failures reconcile to the reviewed input and the failed row can be corrected independently. | Return the parent and site identifiers, the selected manual or import path, prerequisites, validation cases and recovery steps. Preserve ticket history when proposing a correction. Before deactivating or restoring a site, check current references and upstream synchronization. For live API or runbook work, inspect tenant capabilities and validate the mapped fields. Halo documents native runbook actions to create and edit sites. [Custom Integrations/Runbooks](https://www.usehalo.com/guides/1630) ## Record the migration decisions Use the tenant's actual import template. The following columns are for the planning and reconciliation worksheet. | Review field | Record | | --- | --- | | Source key and parent key | Stable identifiers from the authoritative systems, with matching rules and owner. | | Target customer and Site ID | Existing or returned Halo IDs, with display names for review. | | Intended operation | Create, update, leave unchanged or resolve conflict. | | Dependent records | Counts of users, assets, site contacts and routing or portal rules affected by the change. | | Approval and validation | Reviewer, pilot result, successful record evidence and exception reason. | | Recovery | Previously exported values, proposed correction and check for in-flight tickets or sync writes. | Where end users can select among sites, verify the relevant ticket logging setting in **Configuration > Self-Service Portal**, then test a restricted user and a user with access to several sites. [Self Service Portal Settings](https://www.usehalo.com/guides/1862)