> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/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/command-centre/accessnow-user-guide/system-administration/user-management.md).

# User Management

## Single-Sign-On Users

The Single Sign-On (SSO) feature is part of the new AccessNow account setup. SSO integration is configured in collaboration with the customer's IT department. Once configured, users can log into AccessNow seamlessly, without needing a username or password.

Users are automatically created in AccessNow through Single Sign-On (SSO) integration. However, it is also possible to [create users beforehand](/command-centre/accessnow-user-guide/system-administration/user-management/creating-and-updating-a-user.md), such as for configuring the system.

{% hint style="warning" %}
Channel partners responsible for configuring AccessNow should be part of their customers' Single Sign-On (SSO) infrastructure.
{% endhint %}

## User List

All AccessNow users are visible in the **Users** module. SSO users appear in the AccessNow user list **after logging in for the first time**.

<figure><img src="/files/tw4MC9atv6Urjj7OA3qC" alt=""><figcaption></figcaption></figure>

<details>

<summary>Non-Single-Sign-On Users used for the AccessNow account configuration</summary>

For channel partners who cannot use their customers' Single Sign-On (SSO) to access AccessNow, there is an option to use non-SSO accounts. These accounts should be used temporarily and only as an exception.\
\
**All non-SSO users must configure and use two-factor authentication.**

{% hint style="danger" %}
**Update on Privileges for Non-SSO Users**\
Once the system configuration is complete, delete non-SSO accounts or align their privileges with the Channel Partner/Security Installer tasks in AccessNow, such as workflow maintenance. For example, assign them to the "Workflow Managers" group to allow workflow maintenance.
{% endhint %}

</details>


---

# 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://help.security.gallagher.com/command-centre/accessnow-user-guide/system-administration/user-management.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.