> For the complete documentation index, see [llms.txt](https://docs.cow.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cow.tech/using-cow/navigation/integrations/autotask-psa/autotask-permissions.md).

# Autotask Permissions

To enable secure warranty sync while following least privilege principles, you’ll need to create a dedicated API account and role.

## API Security Levels setup

1. Go to Admin > Account Settings & users > Security Levels
2. Make a copy of API User (system) (API-only)
3. Click on "No Permission" for all items to prevent setting incorrect permissions
4. Click on the "CRM" header
5. Add "Customer & Cancelation" with "All" permission
6. Add "Configuration Items & Subscriptions" with "View All" and "Edit All" permissions
7. Click on the "Inventory" header
8. Add "Products" with "View All" permissions
9. Click on the "Admin" header
10. Check the box for "Configuration Items"
11. Save this permission with your own name, such as "COW Warranty Permissions"

**API account Setup Steps**

1. Go to **Admin >** Resources/Users **> API Members**
2. Create a new API user. Select the security level created above.
3. Setup the API account according to your own procedures, giving it an email, internal location, and generate the credentials
4. Select the "CyberDrain B.V." API Tracking integration vendor.
5. Save the account and enter your credentials in cow\.tech.


---

# 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.cow.tech/using-cow/navigation/integrations/autotask-psa/autotask-permissions.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.