> For the complete documentation index, see [llms.txt](https://docs.violetlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.violetlabs.com/apps/a/asana/optional-connect-using-a-pat.md).
# \[Optional] Connect using a PAT
If you prefer to connect Asana using a Personal Access Token (PAT), follow the instructions below to generate one.
Once you're done, head back to [Apps](https://app.violetlabs.com/apps/) in Violet (or [Apps](https://app.violetgov.com/apps/) in VioletGov), click **Show other authentication options**, enter your token, and click **Connect with API Token.**
### Generate a Personal Access Token in Asana
1. In Asana, navigate to your profile icon in the top right corner and click **My Settings**
.png?alt=media&token=258cc5db-886c-42e1-950a-fc9dae5fcd41)
2. In the top menu, select **Apps**, then **Manage Developer Apps** to navigate to the Asana developer console.
.png?alt=media&token=9c355400-18b0-4616-a388-62cee26880e1)
3. Select **Create new token**, then give the token a descriptive name, select the checkbox to agree to the Asana API Terms, and click **Create token**. Copy it down - you're done!
.png?alt=media&token=162f97dc-233d-451b-b735-363446229c58)
---
# 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.violetlabs.com/apps/a/asana/optional-connect-using-a-pat.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.