> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/users-and-roles/user-management/self-service-read-only-users/create-the-self-service-read-only-users.md).

# Create the Self-Service Read-Only Users

If you have an enterprise directory and central authentication is configured on Cortex XSOAR, and if the self-service read-only user configuration is set, then you do not need to do anything to create the user. Any user logging into Cortex XSOAR with a valid enterprise username and password, but without any role associated in Cortex XSOAR’s user’s configuration, will be treated as a read-only user and will enter the Cortex XSOAR self-service portal.

However, if there is no enterprise directory and central authentication, then you need to create such users. To do this, create a temporary role and assign it to the user. After you create the user, delete the role, so the user will appear in Cortex XSOAR with no role.

In either case, read-only users do not count as users in your license pool.

Before creating users, verify you have [configured the server for self-service read-only users](#UUID-9563d2dd-2b56-f6e0-65dc-29173804bc33).

1. Go to **Settings > Users and Roles**.
2. Click the **Roles** tab.
3. Click **New**.
4. In the Role Name field, type the name for the new role. you do not need to assign it any permissions.
5. Click the **Users** tab.
6. Click **Invite User**.
7. Enter the user’s email address, select the role you created, and click **Invite**.
8. Click the **Roles** tab and delete the role you created.


---

# 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://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/users-and-roles/user-management/self-service-read-only-users/create-the-self-service-read-only-users.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.