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

# Partner data and trust expectations

> The questions every integration should answer before it handles customer or financial context.

<Note>
  **Status:** Planned: a future or partner-dependent direction, not a current capability.
</Note>

## Before access is granted

1. **Name the data** - Document the fields, events, identifiers, retention, and environments the integration needs.
2. **Name the authority** - For each state, identify whether LevelSell, the provider, or the partner is authoritative.
3. **Name the failure path** - Describe retries, timeouts, partial delivery, revocation, and support escalation.
4. **Prove the boundary** - Test tenant isolation, role permissions, redaction, and replay handling before production access.

## Protected domains

<Warning>
  **No partner shortcut around finance truth**

  Payment, ledger, commission, payout, access, and refund decisions cannot be delegated to a client-side integration or partner dashboard.
</Warning>

## Open partner decisions

* Which public API and event version should partners target?
* What webhook signing, replay window, and rate-limit policy will apply?
* What support response times and incident communication model will be published?
* Which data-processing, deletion, and regional hosting commitments are required for each partner class?