Skip to main content
System and administration

Importing agents and organization settings

Import or refresh your agents from HaloPSA, Autotask or ConnectWise PSA, invite the ones who need a login, and manage the organization's display name, company domains and domain verification.

Last updated 21 days ago

The Import and Organization tabs of Team Management do two jobs. Import brings your PSA's agents (resources on Autotask, members on ConnectWise PSA) into QuantumOps so that they appear in the list. Organization holds the name your organization shows at sign-in and, with some sign-in services, the company domains. Administrators use both.

Before you start: you need the Administrator role, and your PSA must be connected. See Your HaloPSA connection, Connect Autotask or Connect ConnectWise PSA.

Import agents from HaloPSA

On Autotask and ConnectWise PSA the same tab imports your resources or members, and the button reads Import all resources from Autotask or Import all members from ConnectWise. The rest of this section describes HaloPSA; the counts and the log work the same way.

The setup wizard's Import Agents box, which is checked by default, runs this same import when you complete setup, so most instances start with their agents already imported. Use this tab to import again, for example when HaloPSA gains new agents or the wizard reported that some agents failed. See The setup wizard. The Initial Data Import screen offers the same import.

  1. Open Team Management and select the Import tab.

  2. Select Import all agents from HaloPSA. The button reads Importing… while it works. A progress bar and a running log show each agent as it is imported, one at a time.

  3. When it finishes, read the counts under the log:

    CountMeaning
    ImportedAgents that were added or updated.
    SkippedAgents that HaloPSA returned without an id. They are not a failure.
    FailedAgents that could not be imported. The log names each one with the reason.

  4. Select Clear results to hide the log and the counts.

If QuantumOps cannot fetch the agent list from HaloPSA, the log says Failed to fetch agents with the reason and Failed shows 1. Check your HaloPSA connection and run the import again.

Run the import again whenever HaloPSA gains new agents. An agent already in QuantumOps is updated, not duplicated:

  • Its name, e-mail address and team are refreshed from HaloPSA.
  • Shift hours, agent role, extension number and the other details you keep in Team Management are left as they are.
  • Mark as inactive is left as it is. An agent you marked inactive in Team Management stays inactive after an import, and stays out of the routing and status lists; clear the mark in the person's Edit team member dialog to bring them back.

Invite the agents you imported

Imported agents cannot sign in. Until they are invited, each appears in the list as Agent only.

The Recently imported card appears under the counts. It lists the agents from this run. Next to each one you see Has a login if they already have one. Otherwise, if the agent has an e-mail address and your sign-in service can invite, you see Invite. Select it to open the invitation dialog with their address filled in. The steps are in Inviting people, roles and agent links.

The card is only a shortcut and disappears when you leave the tab or clear the results. You can always invite someone later from the Team Members tab.

Rename the organization

Select the Organization tab. The first card, Organization identity, has three boxes:

  • Billing name is read-only. It is managed in Tenant Settings. See Tenant settings.
  • Display name is how your organization is named to people signing in and in the invitations they receive.
  • A third box shows the organization's id in your sign-in service. It is read-only.

To rename, change Display name and select Save organization settings. The name is renamed in your sign-in service as well. With Zitadel, a hint under the box shows the name Zitadel holds when it differs from yours and says that saving renames it.

With Zitadel, a rename changes more than the name, so QuantumOps asks you to confirm first. The question names the old and new name and explains that Zitadel builds the organization's default domain from its name. That domain changes too, and any login name that ends in it changes with it. Select Rename to continue, or Cancel to stop before anything is saved.

If the display name saves but the sign-in service refuses the rename, a warning begins Settings saved, but.

The Multi-user access card shows a Multi-user or Single user pill that says whether several people can sign in with roles. It is read-only here. A note beginning Single-user mode means multi-user access is off. The note points to the Setup Wizard (its Billing & Organization step), because Tenant Settings has no multi-user switch. If you cannot switch it on there, contact TechPulse. See Getting help.

The Related settings card links to Full tenant settings and Q-Director settings. See Tenant settings and Q-Director settings.

Domains depend on your sign-in service

The domain cards appear only when multi-user access is on and your instance has a sign-in organization. Company domains are managed here with Auth0 and with Zitadel. With a sign-in service that has no per-organization domains, the tab shows a Domains and enterprise sign-in card instead. It explains that sign-in with Microsoft Entra ID and other enterprise providers is set up once for the whole sign-in service, not per organization, so there is nothing to connect here, and that you invite people from the Team Members tab. If domains were saved earlier, the card lists them and says they are kept in the tenant settings.

The rest of this page applies to Auth0 and Zitadel. The differences are marked.

Add and verify a company domain

A verified domain lets people from your company sign in to this organization. With auto-membership on, they also join it without an invitation.

  1. Under Organization domains, enter the domain, for example yourcompany.com, in Add domain and select Add domain, or press Enter. The domain needs a dot and at least 4 characters, and each domain can be added once.
  2. Select Save organization settings. Until you save, the domain shows Not registered. After you save, it shows Pending.
  3. Select DNS setup beside the pending domain. A panel shows the Host and the TXT value. Use the copy buttons beside each.
  4. At your DNS provider, add a TXT record with that host and value.
  5. Select Verify now. QuantumOps checks your DNS every 10 seconds for up to 5 minutes. The button reads Checking… (stop) meanwhile; select it to stop early. When the record is found and your sign-in service confirms it, the domain shows Verified and a message says so. With Zitadel, add the record and verify within one hour: a fresh record is issued after that, and the panel shows its new value.

If the 5 minutes pass before the record is visible, select Verify now again.

To remove a domain, select the cross beside it and then Save organization settings. This removes it from your sign-in service only while at least one other domain remains; to remove your last domain, contact TechPulse. With Zitadel, only domains that an earlier save from QuantumOps added are removed: a domain someone added directly in Zitadel stays.

To let people join without an invitation, check Auto-membership on domain match and save. People who sign in with a matching e-mail domain then join the organization without an invitation. With Zitadel, this turns on domain discovery for the organization, which works only once one of your domains is verified, so save again after verifying a domain. If it could not be applied, the save reports Settings saved, but: followed by Auto-membership: and the reason.

Check the DNS records

Under the domains, DNS record health check looks for each domain's TXT record at your DNS provider, independently of what your sign-in service reports. Select Check DNS records. For every domain you see the sign-in service's status, labeled with its name (for example Zitadel: verified), and whether the record was found. When the record is missing, the check shows the host and value to add again. A domain that the sign-in service lists as verified but whose record is missing carries a warning, because sign-in by company domain may fail.

Fix a domain verification banner

QuantumOps also checks your domains once a day. A banner reading Domain verification required appears at the top of the page, with the number of domains that need DNS verification. Fix now opens the Organization tab; the cross dismisses the banner for now. Everyone who signs in sees the banner; only an Administrator can fix it from Fix now.

  • A pending domain whose TXT record has appeared is verified automatically at the next daily check.
  • A pending domain whose record is still missing stays in the banner.
  • A verified domain whose TXT record has been removed also appears in the banner. Nothing is deleted, but sign-in by domain may stop working. Add the record again. Check DNS records confirms it is back, and the banner clears at the next daily check.
  • A domain you remove from the organization drops out of the banner at the next daily check.

The banner appears with Auth0 and Zitadel, the sign-in services that verify domains.

Was this helpful?

Still need help? Ask the team