> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/security/security-items.md).
# Security Items
Each security item provides a unique functionality to restrict access to your survey. You can add multiple security items to your survey that will be evaluate from top to bottom until all security items have been authenticated.
{% hint style="warning" %}
The respondent needs to pass all security items checks to access the survey.
{% endhint %}
## ➕ **Adding a security item**
To add a new security item to your survey you may add any of the available security items
🔅 Managing security items
* **`Enable key provider`** will set the security item as a [key provider](/form-management/security/key-provider-concepts.md).
* **`Ignore archived`** will skip any [archived respondent ](/form-management/respondents-management/archived-respondents.md)for his authentication checks.
* **`Logging`** will log any failed / success from the security item in the survey [activity log](/form-management/activity-log.md).
* **`Enabled`** if the security item is enabled is will require the respondent to pass its security checks. You can disable the security item to disable its security check
## 😩 **Failed authentication**
You can trigger specific actions if the respondent fails to authenticate all security items.
* **`Display thanks you message`** redirects the respondent to thank you message page.
* **`Hide survey`** will show a blank page.
* **`Show custom message`** shows a custom message to the respondent.
---
# 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://docs.ngsurvey.com/form-management/security/security-items.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.
