> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/deployr-enterprise/securing.md).
# Securing
DeployR implements multiple security mechanisms for controlling who can run task sequences. It is recommended that you configure at least one of these:
* Entra ID authentication. Leverage the Entra ID device flow for the technician to log in using their Entra ID credentials from a phone or other device.
* Passcode authentication. The technician will log in using a passcode string that has been shared with them by the IT administrator. (Anyone who knows the passcode can use it.)
* Certificate authentication. In an existing OS, a task sequence can be initiated using an existing certificate for authentication so no manual authentication needs to be performed.
It is also possible to bypass authentication altogether by enabling the "Bypass authentication" setting:
With that configured, no authentication will be required from any user; anyone can run any task sequence.
The DeployR client will try the available authentication mechanisms in this order:
1. Anonymous
2. Certificate
3. Windows
4. Entra ID
5. Passcode
If none of these are enabled or configured, the device will continue to ask for a passcode but you will not be able to proceed further.
---
# 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://documentation.2pintsoftware.com/deployr/deployr-enterprise/securing.md?ask=&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.
