> For the complete documentation index, see [llms.txt](https://docs.bird.com/applications/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/applications/settings/account/organization-settings/access-keys.md).
# Access keys
Access keys provide a way to securely access the resources that you need to use without exposing your login credentials.
In the context of Bird, an access key is used to authenticate and authorize an application or user to interact with the Bird APIs.
## Create an access key
1. Go to your **Organization Settings** and click **Access roles**.
2. Click on the **Add new access key** button.
3. Enter a "Key name" and "Key description" that clearly describes the purpose of the access key.
4. From the "Role" dropdown, select the access role that the new access key should be associated with.
5. If you need to add additional access roles to this key, click on the **Add new role** button and select the appropriate role from the dropdown.
6. Once you have selected all the necessary access roles, click the **Create access key button**.
7. Your new access key will be displayed on the screen. Click **Copy**. Be sure to copy the Access key Secret, as it will not be shown again.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.bird.com/applications/settings/account/organization-settings/access-keys.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.