> 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/ignoring-employees.md).

# Ignoring Employees

When you integrate with Microsoft 365 or Google Workspace, Augmentt pulls in **every** account in the tenant — including guest accounts, shared mailboxes, service accounts, and other non-human or non-billable identities. The Ignore feature lets you clean those out of your active Employee list without deleting anything from the source directory.

{% hint style="info" %}
An ignored employee is not assigned an Augmentt license, but they **still receive alerts and automated remediation** if those are enabled for them. Ignoring someone removes them from the licensed employee count — it does not silence their alerts by itself. See [Common issues](#common-issues) below.
{% endhint %}

## Ignore an individual employee

1. Go to the Employees list for the client.
2. Check the box to the left of the username you want to remove.
3. An **Ignore** button appears in the top-right corner once a box is checked.
4. Click **Ignore** — the employee moves from the Total Employees list to the Ignored Employees list.

## Ignore multiple employees at once

You can multi-select employees or filter by any column first. For example, filter to show only unlicensed users, then select and ignore all of them in one action — much faster than ignoring one at a time in larger environments.

## Unignore an employee

1. Click on the **Ignored Employees** box/filter.
2. Select the user(s) you want to restore.
3. Click **Unignore** on the right side of the page.

{% hint style="warning" %}
If Unignore doesn't seem to work — the employee stays ignored, or the action is blocked with a message about needing to change Import Settings first — check your [Import Settings](/configuration/import-settings.md) configuration for that client. Import Settings rules can override a manual unignore, so the two features interact: an employee excluded by an Import Settings rule may need that rule adjusted before an individual Unignore action will stick.
{% endhint %}

## Common issues

**"I ignored a user but I'm still getting alerts for them."** This is expected behavior, not a bug — ignoring an employee stops license assignment, but alerting and automated remediation continue to apply to them unless you separately disable alerts/remediation for that user or adjust your alert rules. If you need alerts suppressed entirely for a specific person, that needs to be handled through your alert configuration, not through Ignore alone.

**Guest/external users inflating your counts.** Guest accounts typically have no license and get auto-classified into the ignored bucket in most environments, since they have no license assigned — but this depends on your Import Settings configuration for that tenant. If you need external/guest users excluded from reporting and licensing insights scope more broadly (not just hidden from the active list), that's an Import Settings question — see [Import Settings](/configuration/import-settings.md).

**Deactivated companies still showing users in totals.** If a company has been deactivated but its users are still counting toward totals somewhere in the UI, that's a separate issue from Ignore — flag it to support rather than trying to fix it via employee ignoring.


---

# 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/ignoring-employees.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.