Setup wizard: HaloPSA and your organization

Steps 2 and 3 of the setup wizard connect QuantumOps to HaloPSA and set up your organization, the group of people who can sign in to your instance. Only an Administrator can use them.

Before you start: create the API application in HaloPSA first. Your HaloPSA connection shows how and lists the permissions the application needs, so this page does not repeat those steps. You need the HaloPSA address, the Client ID and the Client Secret in hand.

Step 2 opens with Choose your PSA while your instance has no tickets yet: HaloPSA, Autotask or ConnectWise PSA. This page describes the HaloPSA choice. For the others, see Connect Autotask and Connect ConnectWise PSA; step 3 is the same on every PSA. After the first ticket arrives the choice is locked, because every id QuantumOps stored belongs to the PSA you picked.

Step 2: connect HaloPSA

1. Enter the HaloPSA Agent URL: the address of your HaloPSA instance without https://, for example yourcompany.halopsa.com.
2. Enter the Client ID and the Client Secret from the API application. The secret is hidden as you type.
3. Choose your Region and your Version, described below.
4. Select Test Connection. The result appears under the button: Connection Successful!, or Connection Failed with the reason.
5. Optionally exclude ticket types, as described in the next section.
6. Choose Next.

Next stays unavailable until the address, Client ID, Client Secret and Region are filled in and a test has succeeded. If you edit the address, the Client ID or the Client Secret after a test, the result is cleared and you test again.

The test result is not remembered. Each time you open this step, including when you come back to it or reopen the wizard later, choose Test Connection again before Next and Select Types become available.

QuantumOps connects to HaloPSA at the Agent URL, with the Client ID and the Client Secret. Region and Version are recorded with your tenant and do not change how it connects. QuantumOps stores the credentials encrypted. To change them later, use the HaloPSA Integration section of Tenant settings.

Exclude ticket types from AI processing

Ticket Type Exclusions is optional. It stays locked until a connection test succeeds, because the list of ticket types is read from your HaloPSA instance.

1. Select Select Types.
2. In Select Ticket Types to Exclude, select the types QuantumOps should leave out of AI processing, such as internal tickets or recurring jobs. Check that the names match your own HaloPSA ticket types.
3. Select Apply Selection.

The box next to the button then lists the excluded types by number. It reads No ticket types excluded when nothing is excluded.

Step 3: billing and organization

Three fields are required: Billing Name, Country and Organization Name. Everything else on the step is optional.

Billing information

Under Billing Information, enter the Billing Name (a company or an individual) and the Country. QuantumOps uses the country to work out tax on your billing address. Address Line 1, Address Line 2, City, State/Region and ZIP/Postal are optional.

Spending controls and time zone

Monthly Limit takes an amount per month. The preset buttons fill in common amounts, and Unlimited sets no limit. You are warned at 80% of the limit, and AI processing pauses when the month's spend reaches it. It resumes next month, or when you raise the limit. Tenant settings calls the same figure AI Consumption Limit ($) and explains what it does.

Display Time Zone sets the time zone used to show dates and times. The current time in the chosen zone appears under the field.

Your organization

The organization controls who can sign in to your instance. Multi-User Organization is always on and cannot be switched off.

1. Enter the Organization Name. People see this name when they sign in or receive an invitation.
2. Select Create Now when the panel below the field says the organization is ready to be created. QuantumOps creates the organization with your sign-in service and adds you to it as an Administrator.
3. Once the organization exists, the panel reads Organization Active. Select Sync to send the name to the sign-in service again after you change it. Sync also sends the domains and membership settings where your sign-in service supports them.

If you skip Create Now, completing step 12 creates the organization for you. If your instance came with an organization already, the panel shows Organization Active from the start.

Company e-mail domains

Domains identify your company's e-mail addresses. They are optional, and you can add them after setup. Domains are stored with your organization. Auth0 and Zitadel verify them and add members by domain; see what each sign-in service offers. With a sign-in service that does not, such as Microsoft Entra ID, the list is saved and nothing else appears on this step. See Importing agents and organization settings.

1. Under Organization Domains, type a domain such as yourcompany.com and select the plus button next to the field.
2. To remove a domain, select the cross on its tag.

When your sign-in service supports domains, QuantumOps sends the list to it when you select Create Now, select Sync, or complete setup. With Zitadel, a sync removes only domains that an earlier save from QuantumOps added and you have since taken off the list: a domain added directly in Zitadel stays, and an empty list removes nothing. If some domains cannot be synced, a warning beginning Domains could not be fully synced: says which.

Auto-Add Members by Domain is a switch for adding people whose e-mail address matches one of your domains to the organization when they sign in. The wizard saves your choice. It has an effect only where your sign-in service adds members by domain. With Zitadel it turns on domain discovery for your organization, which works only once one of your domains is verified, so save again after verifying. A warning beginning Auto-add members by domain was not applied: says when it could not be applied. Where your sign-in service does not support it, invite people instead. Test it with a colleague's account after setup.

Verify a domain

This applies only when your sign-in service verifies domains. Each domain then shows Pending until its ownership is proved and Verified afterwards. A domain that shows no status has nothing to verify from this screen. To verify a pending domain:

1. Select Setup DNS next to the domain. The DNS Verification panel opens.
2. At your DNS provider, add a TXT record with the Host / Name and the Value shown. The Record Type is TXT. The copy buttons copy each value.
3. Select Verify Now. QuantumOps checks DNS every 10 seconds, up to 30 attempts, and shows the attempt number and what it found. When it finds the record, the sign-in service verifies the domain and the tag changes to Verified. With Zitadel, add the record and verify within one hour: a fresh record is issued after that.
4. DNS changes can take a while to spread. Select Checking... (Click to stop) to stop, and try again later. Close hides the panel.

Invite team members

You can invite your team after setup from Team Management, which offers invitations wherever your sign-in service supports them. See Inviting people, roles and agent links. The wizard's Invite button works only with some sign-in services. If it does not send an invitation, skip it and invite from Team Management.

If you use the wizard's button, Invite is unavailable until the organization exists.

1. Select Invite.
2. In Invite Team Member, enter an e-mail address.
3. Select Send Invitation.

When the invitation is sent, the person receives an e-mail with a link to set up their sign-in. See Activating your account for what they do next. People you invite here are listed under Team Members on the step. Invitations sent from the wizard carry no roles, so assign roles afterwards in Team Management.

Related pages

• The setup wizard for how the steps work together.
• Your HaloPSA connection for creating the API application.
• Tenant settings for changing these values later.
• Importing agents and organization settings for bringing in your HaloPSA agents and managing the organization after setup.