> For the complete documentation index, see [llms.txt](https://docs.aviator.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aviator.co/mergequeue/how-to-guides/personal-access-tokens.md).

# How to Create Personal Access Tokens

Learn how to connect your app using a Personal Developer token instead of using Aviator app authentication when connecting as a GitHub app has limitations.

There are some scenarios where connecting as a GitHub app may have certain limitations (for instance using SAML restricted authentication). In such cases, you should connect your app using a Personal Developer token instead of using Aviator app authentication.

To do so, you can create a personal developer token and [<mark style="color:blue;">set the token here</mark>](https://mergequeue.com/github/auth/dev_token). You can find instructions on how to [<mark style="color:blue;">generate a token here</mark>](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token)<mark style="color:blue;">.</mark> You may create a separate GitHub user for this purpose. If you choose to only connected Personal Access token, you may have to also setup custom webhooks to send requests to Aviator. Please contact us at [<mark style="color:blue;">howto@aviator.co</mark>](mailto:howto@aviator.co) for details.


---

# 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.aviator.co/mergequeue/how-to-guides/personal-access-tokens.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.