> For the complete documentation index, see [llms.txt](https://helpdesk.augmentt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdesk.augmentt.com/configuration/offboarding-a-client.md).

# Offboarding a Client

When you stop servicing a customer, you'll want to fully remove them from Augmentt — both the account record in the portal and any lingering access Augmentt still has inside their Microsoft or Google environment. Follow these steps in order.

{% hint style="info" %}
This is different from **offboarding an end user** (an employee leaving a client company). That process — converting mailboxes, revoking licenses, disabling the account — lives in Augmentt Engage's user offboarding workflow, not here. This article covers removing an entire **client/company** from your Augmentt tenant.
{% endhint %}

## Step 1: Disconnect the Microsoft or Google integration

In the Augmentt portal, go to **Configuration > Integrations**, find the connected integration (M365 or Google Workspace) for the client you're offboarding, click the three dots in the top-right corner of that integration card, and select **Disconnect Integration**.

**Optional cleanup for M365 clients:** you can also remove the Augmentt Engage Enterprise Application from the client's Azure AD/Entra tenant:

1. Log in to the Azure portal at [aad.portal.azure.com](https://aad.portal.azure.com/).
2. Select **Enterprise Applications** from the navigation menu.
3. Click on **Augmentt Engage** in the application list.
4. Select **Properties**, then click **Delete**.

This step isn't required to disconnect the integration, but it clears out any remaining Augmentt footprint in the client's Microsoft environment — useful if the client (or their compliance team) wants confirmation that no third-party app access remains.

## Step 2: Uninstall the Augmentt Agent (if deployed)

If the client had the Augmentt Agent installed for Discover, uninstall it from their endpoints as part of the offboarding process.

## Step 3: Deactivate the company

In the Augmentt portal, go to **Configuration > Companies**, click the three dots to the far right of the company you're removing, and select **Deactivate Company**.

{% hint style="success" %}
Deactivated companies aren't deleted immediately. They're retained for **30 days**, during which you can reactivate the account without losing data or users — useful if a client comes back, or if you deactivated the wrong company by mistake.
{% endhint %}

## Deleting a deactivated company permanently

If you want a deactivated company removed outright rather than waiting out the 30-day retention window, go to **Configuration > Companies**, find the deactivated company, click the three dots, and select **Delete Company**. After 30 days, deactivated companies age out and are removed automatically — this manual delete option is for when you don't want to wait.

## Related settings you may want to check first

Before fully offboarding, it's worth reviewing 2FA/MFA settings for any users still tied to the account — see [Enabling 2FA for Portal Users](/configuration/enabling-2fa-for-portal-users.md). If the client used Google Workspace rather than M365, note that scheduled offboarding for individual Google Workspace users currently isn't available in Engage the same way it is for M365 — plan for a manual process if you're offboarding GWS end users as part of this cleanup.

## Common issues to watch for

| Issue                                            | What to know                                                                                                                                                                             |
| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Company won't go away after "Delete"             | Deactivated companies are retained 30 days by design before permanent removal; deletion isn't instant.                                                                                   |
| License Center still lists a deactivated company | This has been reported after deactivation — if a deactivated company keeps showing up where it shouldn't (e.g., License Center), contact support rather than assuming it's still active. |
| Reactivating after deactivation                  | Reactivation within 30 days restores data and users — after that window, the company (and its data) is gone.                                                                             |

{% hint style="warning" %}
Exact UI labels for individual steps (e.g., whether it reads "Delete Company" verbatim in every portal version) weren't independently verifiable in this session — confirm current wording against the live portal before treating this as pixel-exact.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpdesk.augmentt.com/configuration/offboarding-a-client.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
