> For the complete documentation index, see [llms.txt](https://docs.locoia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.locoia.com/embed-white-label-portal/embed-admin-setup/4.-embed-for-end-user.md).
# 4. Embed for End User
User journey: Embed activation process
End users go through the following process when opening the Embed iframe for the first time:
1. [(optional) Give consent (Consent screen)](#consent-screen)
2. [View the list of groups with integrations](#displaying-of-groups-and-flows)
3. [Setup integrations](#integrations-setup)
## Consent screen
If Embed is configured with the setting "Ask for consent", then an end user will see a [Consent screen](/embed-white-label-portal/embed-admin-setup/2.-configure-embed/consent-screen.md) before being able to access the iframe.
## Displaying of Groups and Flows
If there are multiple groups in an Embed Configuration they are collapsed by default.
If there's only one group in an Embed configuration, the group is expanded by default and if that group has only one Flow, it's already on the first step of the activation process when the Embed is opened.
If the user clicks the "Delete all my integration data" button in the iframe, they will be asked for consent again, the next time they open the iframe.
## Integrations setup
The set up for each integration shows all systems (Connectors) that expect user input. The user then provides information step by step. It is not possible to switch between the steps.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.locoia.com/embed-white-label-portal/embed-admin-setup/4.-embed-for-end-user.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
