> ## Documentation Index
> Fetch the complete documentation index at: https://help.avoca.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Data Export

> Enable, schedule, monitor, pause, and remove supported recurring exports for a team.

Open **Settings → Integrations → Data Export**. Only team admins can configure exports; other members see an admins-only notice.

The current catalog includes **Searchlight**, which sends Simple Scheduler booking data to Searchlight through its configured S3 destination on a recurring schedule. The dashboard shows only the destinations Avoca currently supports.

## Enable an export

1. Expand the destination card.
2. Review its description and current status.
3. Choose the available **Frequency**.
4. Choose **Enable**.
5. Confirm that the card shows **Enabled** and review its next-run time.

An enabled card exposes the current status, frequency, last run, and next run.

## Operate an existing export

* Use the status switch to pause or resume scheduled runs.
* Change **Frequency** to update the recurring cadence.
* Choose **Run now** to queue a manual run. The export must be active.
* Choose **View history** to inspect recent runs and their results.

If a card is labeled **Enterprise-managed**, its configuration applies to this team but is owned by an enterprise admin. The team page is read-only for that export; ask the enterprise admin to change its frequency or status.

<Warning>
  **Disable** removes the export configuration and its run history. You can enable the destination again later, but the deleted history cannot be recovered. Use Pause when the interruption is temporary.
</Warning>

## Validate an export

1. Confirm the card is enabled and not enterprise-managed when you intend to edit it.
2. Review the frequency and next run.
3. Use **Run now** for an approved test.
4. Open **View history** and confirm the run completes successfully.
5. Confirm the expected records in the destination with its owner.

If enabling a team export reports that the destination is already covered at the enterprise level, do not create a second configuration. Ask the enterprise admin to manage the existing export.

If a run fails, record the destination, run time, and visible non-secret error. Contact Avoca Support without attaching exported customer data or destination credentials.