> 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/installation-setup/system-settings/saml-settings.md).

# SAML

The SAML settings allows you to setup a link between ngSurvey and your SAML identiy provider to let SAML users log into ngSurvey using their existing Entra credentials.

## 🔅SAML properties

* **`SP Entity Id`**  your SAML SP entity ID. 
* **`Entity Id`** Real entity of the SAML provider.
* **`Identity provider single singon URL`** SAML provider logon URL.    
* **`Identity provider signing X509 certifacte`** signing key that will be used to validate the SAML responses.
* **`Service provider assertion consumer service URL`** ngSurvey that will be called by your SAML provider to validate the assertions.  

Here an example of a SAML configuration, replace the values accordingly to your SAML identity provider. \ <br>

<figure><img src="https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8fLhS0bmfBRyq0HdUm%2Fuploads%2FlWffqvsXTTeY21f5kW0T%2Fimage.png?alt=media&amp;token=b33d6c1a-5ad2-4b1d-9af3-6b47adc82f80" alt=""><figcaption></figcaption></figure>


---

# 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/installation-setup/system-settings/saml-settings.md?ask=<question>&goal=<user_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.