> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/system-administration/user-management.md).

# User Management

The **Users module** lists every AccessNow user. It includes:

* **Name**
* **Email**
* **Login Type**, distinguishing between two user types:
  * SSO (Single Sign-On) Users — synchronized from the customer's identity provider, such as Microsoft Entra ID.
  * AccessNow users — created and managed locally in AccessNow.
* **Activity** button — displays the user's requests, approvals, and group memberships. Learn more about [User Activity Tracking](/knowledge-hub/accessnow-user-guide/system-administration/user-management/user-activity-tracking.md).

<figure><img src="https://3605010251-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOxYzVrszbXcNBUauC0e%2Fuploads%2FAzUlXxWyOJQqWWQe8U9O%2FScreenshot%202026-08-27%20at%2017.19.26%20%E2%80%93%20ScreenClip.png?alt=media&amp;token=4334a1a1-85c1-41d4-a5b6-165803df816c" alt=""><figcaption></figcaption></figure>

## Single-Sign-On Users

Single sign-on (SSO) is configured during new AccessNow account setup. Configure the integration with the customer's IT department. Once SSO is configured, users can sign in using their enterprise login and password.

AccessNow automatically creates users through the SSO integration.

You can also [create users manually](/knowledge-hub/accessnow-user-guide/system-administration/user-management/creating-and-updating-a-user.md), for example while configuring the system.

{% hint style="warning" %}
Where possible, channel partners who configure AccessNow should be part of their customer's SSO infrastructure. They can also receive a local AccessNow account when SSO is impractical or unavailable.
{% endhint %}

## AccessNow Users

AccessNow users are created manually in the service. You can provide them to anyone, including people outside the SSO domain. Common uses include system configuration, testing, and granting access to people outside the organisation, such as third-party contractor managers.&#x20;

{% hint style="info" %}
You can convert local users to single sign-on users, and vice versa.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/accessnow-user-guide/system-administration/user-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.