> ## Documentation Index
> Fetch the complete documentation index at: https://kb.mspprocess.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Add your clients

> Add the businesses you support, fix anything that stops a client being ready, and deploy the desktop agent where it's needed.

Clients you imported while [connecting Microsoft 365](https://kb.mspprocess.com/core/get-started/connect-microsoft-365.md) are already on Clients. The line above the table lists anything that stops a client being ready.

<video controls preload="none" playsInline poster="/images/videos/add-your-clients.jpg" src="https://mintcdn.com/triggr/rFRD51HB_88hTzdJ/images/videos/add-your-clients.mp4?fit=max&auto=format&n=rFRD51HB_88hTzdJ&q=85&s=a02f06d4c1f96829e2f8208cc306b4a6" />

Add your clients: adding one, fixing what isn't ready, the desktop agent and checking Microsoft access (1:27).

![The Clients page with Connection Audit, Import and Add client buttons, a readiness summary line, and a table of clients with Environment, Agent, Microsoft and PSA columns.](https://mintcdn.com/triggr/MwzXHG3UWzFixdSz/images/core/add-your-clients/clients-page.png?fit=max\&auto=format\&n=MwzXHG3UWzFixdSz\&q=85\&s=b7232a36f1c0a83c645df9d621842756)

Clients. Needs attention filters to clients with a gap.

## Add clients

> [tab] Import from Partner Center
>
> With a GDAP connection, click **Import > Microsoft Partner Center**, tick the customers and click Import. Then click **Link all** on Clients to link them to GDAP.

> [tab] Add one yourself
>
> Click **Add client**. Enter the Primary domain and Core fills in the Microsoft tenant ID, which your public forms use to recognise the client's staff.
>
> ![The Add a client dialog with Client name, Environment set to Cloud Only, an optional Primary domain and an optional Microsoft tenant ID.](https://mintcdn.com/triggr/MwzXHG3UWzFixdSz/images/core/add-your-clients/add-client.png?fit=max\&auto=format\&n=MwzXHG3UWzFixdSz\&q=85\&s=1257751e99f891e68d9e671fc7a8ad18)

Choose Cloud Only for Microsoft 365-only clients. The On-Prem options are for clients with on-premises Active Directory and need the [desktop agent](#deploy-the-desktop-agent); choose synced when AD syncs to Microsoft 365, so Core makes [user changes in AD](https://kb.mspprocess.com/core/reference/workflow-catalogue.md#clients-with-on-premises-ad).

## Fix what's not ready

Click a client. Readiness shows a button for each gap: Link to GDAP, Add tenant ID, Approve access (per-client app, as the client's admin) or Map to *your PSA*. Under Details, fields save as you leave them, and Look up from domain fills in the tenant ID.

![The Initech client panel with Readiness showing Microsoft Not linked with a Link to GDAP button and PSA Not mapped with a Map to Halo button, above the Primary domain, Microsoft tenant ID with Look up from domain, and Environment type fields.](https://mintcdn.com/triggr/MwzXHG3UWzFixdSz/images/core/add-your-clients/client-drawer.png?fit=max\&auto=format\&n=MwzXHG3UWzFixdSz\&q=85\&s=58abdcdea37d00b0c35612228358b91a)

## Keep an eye on Microsoft access

With GDAP, Triggr connects each linked client by itself and checks every GDAP client overnight. Click a client's Microsoft status to open GDAP health; Check now rechecks it, and Check all and Repair all above the table cover every client.

* Setting up…: Triggr is connecting the client or fixing it. Nothing to do.
* A warning, such as Needs a GDAP role: follow the steps in GDAP health, or click **Ask the assistant**. Each warning is in [Fix Microsoft connection problems](https://kb.mspprocess.com/core/reference/fix-microsoft-connection-problems.md).
* Expires in *N* days: extend the GDAP relationship in Partner Center. Expiring lists these clients.

![GDAP health showing App not consented with Repair and Check now buttons, and checks for Microsoft sign-in, Graph permissions, Admin roles, GDAP relationship and Recent failures.](https://mintcdn.com/triggr/MwzXHG3UWzFixdSz/images/core/add-your-clients/gdap-health.png?fit=max\&auto=format\&n=MwzXHG3UWzFixdSz\&q=85\&s=15946d35b88336c73e7719d95c3f8efe)

To test a client's access live, click Check permissions under Microsoft connection, or run [Connection Audit](https://kb.mspprocess.com/core/manage/gdap-alerts.md#check-microsoft-access-for-every-client) for every client.

## Deploy the desktop agent

Clients with on-premises Active Directory have an Agent section in their panel.

**1. Generate credentials**

Click **Generate agent credentials** and copy the Client ID and secret, then click Done — hide secret. The secret shows once; Regenerate replaces it and revokes the old one.

**2. Install the agent**

Run the [install script](https://kb.mspprocess.com/desktop-agent/install.md) as administrator on a domain-joined Windows server.

**3. Check it's online**

Click Refresh. The status should read Online; Never connected means the service hasn't reached Triggr yet, so check the script's output.

![The Agent section of a client panel showing an Online status, Last seen and Last authenticated times of 1 min ago, a Refresh button, and the Client ID with a Copy button.](https://mintcdn.com/triggr/MwzXHG3UWzFixdSz/images/core/add-your-clients/agent-section.png?fit=max\&auto=format\&n=MwzXHG3UWzFixdSz\&q=85\&s=e2285a85e9e2a6721a75cc38e0b40d57)

For a Cloud + On-Prem (synced) client, then set its OUs on the [On-premises AD card](https://kb.mspprocess.com/core/get-started/configure-user-onboarding.md#settings-for-each-client).

## Troubleshooting

> [accordion] “Couldn't find a Microsoft tenant for that domain”
>
> Check the domain, or paste the tenant ID from the client's [Microsoft Entra admin center](https://learn.microsoft.com/en-us/entra/fundamentals/how-to-find-tenant).

> [accordion] “Couldn't link this client — add its Microsoft tenant ID first.”
>
> Fill in Microsoft tenant ID under Details, then click **Link to GDAP** again.

> [accordion] “Your organisation isn't connected to Microsoft Partner Center”
>
> On the Microsoft setup's Sign in step, click Sign in on Connect Partner Center, then click Try again on the import page.

> [accordion] “Triggr's Microsoft sign-in needs renewing — every client is affected.”
>
> Click Renew, then Redo on Connect Microsoft Graph and Connect Partner Center, signing in as the service account.

> [accordion] A client's staff see “These requests aren't available”
>
> The client's Microsoft tenant ID in Core doesn't match their account's tenant.

Next: [Share your forms](https://kb.mspprocess.com/core/get-started/share-your-forms.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.