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

# How to expose syncs to end-users

A sync needs one setup per end-user: the end-user connects their software and fills the mappings the flow needs. Chift offers three models for that setup. They differ in how much you build and in where your end-user completes it.

Read this page before you write any code. The model you choose decides whether you integrate the Chift API at all.

## The three models

<CardGroup cols={3}>
  <Card title="Embedded" icon="code" href="/syncs/expose-to-end-users/embedded">
    You create the consumer and the activation link from your backend.
  </Card>

  <Card title="Pre-OAuth2" icon="key" href="/syncs/expose-to-end-users/pre-oauth2">
    You share one static URL protected by your own OAuth2 flow.
  </Card>

  <Card title="Marketplace" icon="store" href="/syncs/expose-to-end-users/marketplace">
    Chift hosts a marketplace where your end-users sign up themselves.
  </Card>
</CardGroup>

## Compare the models

| | Embedded | Pre-OAuth2 | Marketplace |
| - | - | - | - |
| Development on your side | Consumer creation, activation link, redirect | None | None |
| Prerequisite | An integration with the Chift API | An OAuth2 flow in your software | None |
| What you give the end-user | A link your backend creates per activation | One static URL per app | One static URL |
| Who creates the consumer | You, through the API | Chift, from your OAuth2 identity | Chift, when the end-user signs up |
| Your end-user needs a Chift account | No | No | Yes, via Google or passwordless sign-in |
| Branding of the setup page | White-label | White-label | Chift marketplace |
| Your end-user manages their own integrations and logs | Only if you build it | Only if you build it | Yes, in the marketplace |

<Note>
  The three models run the same flows. They change who triggers the setup and where it happens, not what the sync does.
</Note>

## Which one to choose

* Choose **embedded** when you want to decide where and when the setup appears in your product, and you accept writing the integration. This is the only model that lets you place the connector choice inside your own interface.
* Choose **pre-OAuth2** when your software already has an OAuth2 flow and you want a white-label experience without writing code.
* Choose **marketplace** when you want no development at all, and your end-users can hold an account in Chift. This model also suits accountants, who manage several client organizations from one account.

## Next

Once you have chosen, follow the page for your model. For the embedded model, continue with [Activating a sync](/syncs/expose-to-end-users/embedded/how-to-activate).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.