> For the complete documentation index, see [llms.txt](https://village-labs.gitbook.io/coworker-product-and-developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://village-labs.gitbook.io/coworker-product-and-developer-docs/data-connections/ashby.md).
# Ashby
### Prequisites
* An Ashby account with sufficient permissions
Important note: the scope of the data which will be synchronized to Coworker is defined by the user behind the API key.\
We recommend that you create a service account which will have the right permissions, ie. no access to sensitive tasks/data.
### Generating the credentials
Log in as the service account which will make the API key, and go to the [API settings page](https://app.ashbyhq.com/admin/api/keys).
Click on "New" to make a new API key.
The scope required for a Coworker connection is the following:
API Key Permissions
Note on the read/write API key permission: Coworker relies on both the standard Ashby API, and webhook data to synchronize your activity.\
When the connection is made, webhooks will be created, [as can be seen here](https://app.ashbyhq.com/admin/api/webhooks). Please do not disable them, as Coworker would become unable to get real-time notifications of your activity.
The read permission on API keys is required for us to be able to verify the creation of these webhooks, as well as clean them up if the connection needs to be deleted.
No other write permission is required, Coworker will not be making any write operation on your data.
### Information required for the Village connection:
* `api_key`: the API key generated above
* `start_date`: the date of the first document that should be synchronized. No document updated before that will be synchronized. Format: ISO8601 date, ie. 2024-05-01T00:00:00Z
---
# 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://village-labs.gitbook.io/coworker-product-and-developer-docs/data-connections/ashby.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.