> 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/getting-started/the-10-step-setup-guide/step-4.-assigning-augmentt-licenses.md).

# Step 4. Assigning Augmentt Licenses

Licensing has two parts:

1. **Who gets imported** — go to **Configuration > Employees > Import Settings** and exclude accounts you don't want Augmentt to manage. You'll typically start with **Exclude from Import > Quick Options > Accounts without licenses**, which covers most guests and service accounts. Ignored employees don't consume licenses and are excluded from posture checks. See the [Import Settings guide](broken://pages/import-settings) for detail.
2. **Who gets licensed** — Augmentt licenses are assigned from **Configuration > Employees**. Secure uses a per-tenant consumption model: enable it for a tenant and every managed employee is licensed automatically, including new employees added later.

Check totals and remaining licenses any time in the **License Center**. Your license pool is a fixed amount you've purchased — it doesn't grow automatically as you add users. If you run out, free some up or contact your account rep.

## What gets licensed automatically

When a tenant connects, Augmentt sees every employee in it but only assigns licenses to accounts that actually need one — primarily licensed users and admin users. Everything else is auto-ignored: shared mailboxes, guest accounts, and non-admin service accounts. Ignored accounts still work normally within Augmentt:

* They can still trigger alerts (e.g. a suspicious sign-in), even without a license.
* Shared mailboxes can still be managed through Augmentt without needing a license — matching how Microsoft itself doesn't require a license for shared mailboxes.

You can also manually ignore individual accounts that don't need monitoring — a test admin account, a conference room phone that requires a Microsoft license, etc. — so they don't consume a license slot or clutter your reports.

## Bulk import by group (large tenants)

For tenants with large numbers of accounts you don't want to manage individually — the classic example is a school, where you want to monitor faculty but not every student — use **Import Settings** to import only members of a specific Microsoft 365 group (e.g. an "All Faculty" group) instead of ignoring each unwanted account one at a time. This can cut a tenant from thousands of imported accounts down to a handful, keeping both your reports and your license usage focused on what you actually manage.

Next: Step 5. Enabling Alert Tickets & Emails


---

# 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/getting-started/the-10-step-setup-guide/step-4.-assigning-augmentt-licenses.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.