> ## 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.

# How partners work with LevelSell

> A clear boundary map for teams integrating with a connected selling platform.

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

## The current partner surface

LevelSell is designed around creator-owned customer journeys: pages and forms capture intent, webinars and products deliver value, checkout verifies payment, CRM keeps context, and workflows coordinate follow-up. A formal public partner API and published service-level commitments are not yet part of the released documentation set.

## Ownership boundaries

* **Frontend:** Presents configuration and returned state, with role-aware routes and protected actions.
* **Backend:** Owns authorization, payment verification, access, CRM mutations, workflow runtime, providers, and audit-worthy side effects.
* **Shared contracts:** Define typed request and response shapes between product surfaces; they are not a replacement for backend policy.
* **Partner system:** Should call an approved integration surface and treat LevelSell identifiers and status responses as external state.

## Integration principles

* Use stable identifiers and server-returned status; never infer payment, entitlement, commission, or payout state from a browser event.
* Make retries safe. Provider callbacks and partner requests must be idempotent at the boundary.
* Keep tenant and role scope explicit on every request and webhook.
* Request the smallest data set needed for the customer outcome.
* Agree on support ownership before launching a joint customer path.