> 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.md). # Self-Service Read-Only Users The self service read-only users feature provides users who do not have an account and at least one role mapped in Cortex XSOAR the ability to access Cortex XSOAR in a very limited capacity. Self service read-only users can: * Create incidents * View their own incidents * Add notes and attachments to their incidents * View the dashboards created for them by the administrator An example of an incident that a self-service read-only user could create is to report that they lost their laptop. Self-service read-only users can only view their own data. They cannot: * start an investigation * create dashboards or reports * change anything in incidents they create To create notes, the self-service read-only user must mark the **`Mark as a note`** option. It is recommended, but not required, that self-service read-only users have an existing account in the company’s enterprise directory and Cortex XSOAR is configured to authenticate and authorize read-only users using the same enterprise directory with LDAP, AD, or SAML authentication protocols. A user is considered as a self-service read-only user if the user has no role associated with the Cortex XSOAR users settings. To enable the self-service read-only user feature, Cortex XSOAR administrators need to: * Set server configuration parameters to: * Allow authenticated users without roles to access the home page. * Define the list of dashboards such users have access to. * Create self-service read-only incident types. Since self-service read-only users cannot initiate an investigation, the playbooks associated with these incident types should run automatically. * Create self-service read-only users if no enterprise directory is configured with Cortex XSOAR. * Create incident layouts for self-service read-only users and allow self-service read-only users to access the incidents tabs containing such layouts. * Create and share dashboards for self-service read-only users. --- # 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.md?ask=&goal= ``` `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.