> 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/troubleshooting/faq.md).

# FAQ

## What PSA platforms are supported?

COW currently supports the following platforms for device synchronization:

* **HaloPSA**
* **ConnectWise Manage**
* **Autotask**

You can also import devices via **CSV upload** if your PSA is not supported.

## How is access controlled?

* Access is scoped by **email domain**.
* The **first person** from a domain to sign up becomes the **org owner**.
* Additional users can be added automatically (via domain match) or manually invited.
* Only approved users can access organisation data.

## What device data is synced?

COW pulls device information from your PSA or CSV source.\
The level of detail varies by manufacturer, but typically includes:

* Serial number
* Purchase or manufacture date
* Model information
* Warranty status
* Service entitlements (if available)

If manufacturer data is incomplete, the device is still tracked but marked with limited metadata.

## Can I import devices in bulk?

Yes. Both PSA-connected and CSV-loaded environments support:

* Bulk imports
* Duplicate detection and de-duplication
* Device removal (if needed)

Note: Devices already synced will not be re-imported unless modified.

## What happens during syncing?

* Only **one sync** runs at a time.
* If a new sync is triggered while one is already running, it will be **queued** and executed afterward.
* This avoids unnecessary load and helps preserve data integrity.

## How often are devices checked?

* Devices are checked when a sync runs. Click **Sync Devices** on the **Devices** page to start one at any time.
* To check a single device straight away, select **Get Warranty** on its row in the **Devices** table.

## Are lookups rate-limited?

Yes. Lookups are subject to throttling to prevent overuse of vendor APIs and ensure reliable responses.\
This helps ensure fairness and availability across all users.

## What manufacturers are supported?

Warranty data is currently available for:

* **Dell**
* **HP**
* **Lenovo**
* **Microsoft Surface**
* **Toshiba**
* **Apple** (devices manufactured before 2022)

Additional manufacturers may be added over time.

## What can I do with the synced data?

Inside the app, you can:

* View all devices and their warranty status
* Export device data (CSV)
* Filter by key attributes (manufacturer, expiry, client, etc.)
* View sync status cards showing:
  * Total devices found
  * Devices pending sync
  * Sync failures or incomplete records
  * Devices with updated warranty data

## Is there a device limit?

Yes.

* **Free Tier**: up to **250 concurrently tracked devices**
* **Pro Tier**: up to **50,000 devices** for **$69/month**
* A **lifetime grace buffer** of up to 400 devices is available for short-term overages.
* If you require more than 50,000 devices, **enterprise options are available**.

## What’s included in the pricing?

* **Free**: 0–250 tracked devices
* **Pro**: $69/month for up to 50,000 tracked devices
* **Enterprise / White-label / Vendor**: Contact us for custom pricing

All subscriptions are **month-to-month**, and you may cancel at any time.


---

# 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/troubleshooting/faq.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.