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

# Embedded

In the embedded model, you integrate the sync setup into your own product. You manage consumers and connections through the Chift API. You call Chift to obtain the activation URL, a page protected by a token, and you decide where and when to share it with your end-user.

This is the only model that requires development on your side. In exchange, you control the experience.

## What you decide

* Where the sync configuration appears in your app.
* When to trigger the sync from your app.
* How to manage the executions of the sync from your app.
* Whether to show execution logs to your end-users in your app.

## What you build

<Steps>
  <Step title="Create the consumer">
    One consumer per end-user. Store the returned `consumerid` on your end-user record.
  </Step>

  <Step title="Create the activation link">
    Call Chift with the `consumerid` and the `syncid`. The call returns a URL secured by a token.
  </Step>

  <Step title="Send your end-user to the link">
    Redirect your end-user to the URL, or email it. Your end-user connects their software and fills the mappings on the Chift-hosted page.
  </Step>
</Steps>

You can also present the connector choice inside your own interface and pass the chosen connector to Chift. See [Two ways to present the choice](/syncs/expose-to-end-users/embedded/how-to-activate#two-ways-to-present-the-choice).

## Next

[Activating a sync](/syncs/expose-to-end-users/embedded/how-to-activate) covers every step with the API calls.


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