> 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/tokens/token-and-querystring.md).

# Token and Querystring

By default a token entry user interface will be shown to the respondent to let him enter his unique code before he can access the survey. There are however cases when you might want to make the token value available to the survey without having to ask the respondent to enter manually his code.\
\
The token security item can automatically retrieve a token value from the browser [query string ](https://www.techopedia.com/definition/1228/query-string)provided that you have set the **Token source variable name**.\
\
As an example if you would have set the in the [token](/form-management/security/security-items/tokens.md) security properties its **Token source variable name** value to **mytoken** then you could append to the [publish url ](/form-management/publish-deploy/web.md)of your survey the token value of your choice as new query string variable.eg:

```
http://yourngsurveysite.com/s/yoursurveyid?mytoken=tokenvalue
```

In the link above the token value **tokenvalue** will automatically be extracted from the query string **mytoken** variable and used by the token security item to log automatically into the survey.  

{% hint style="info" %}
Tokens can also be used in [email campaigns](/form-management/campaigns/campaign/email-distribution.md) invitation message links using the email invitation pipe tag \[\[--invitationtoken-], this tag will be replaced automatically during the campaign sending by one of the available token.   
{% endhint %}


---

# 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/tokens/token-and-querystring.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.