> 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/2.-configure-embed/sharing-level.md).

# 2.3 Sharing level

You can set the sharing level on each Embed and thus e.g. have one embed with user level sharing that you show in the personal settings section in your app and another one that is shared on the account level shown in the admin settings section of your app.

![](/files/-MjUHmVsOZIbTF10NQCh)

{% hint style="warning" %}
The sharing level can only be set during Embed creation and cannot be changed afterwards.
{% endhint %}

Following are some examples using "Company ABC" and the users "John" and "Peter" of that company.

## Embed on user level

Flow that is used by a single user of your customer (e.g. on the personal Slack settings the user can turn on message notifications that happen through a flow). Only the single user will see the exact same state of the flow and also connector auth and can change it.

E.g. John creates a Gmail connector auth and activates the flow. If Peter now goes to the iframe, the flow is not enabled for him and he doesn't see John's Gmail connector auth.

{% hint style="info" %}
The consent screen is in this case shown once per user.
{% endhint %}

## Embed on account level

Flow that is used across the entire account of your customer (e.g. on the Slack Workspace an admin can set to backup all chat data to a FTP server). All other admins of that account will see the exact same state of the flow and also connector auth and could change it.

E.g. John creates a FTP connector auth, activates a related flow and Peter later deactivates the flow and a day later turns it back on using the already existing FTP connector auth.

{% hint style="info" %}
The consent screen is in this case only shown once per account.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.locoia.com/embed-white-label-portal/embed-admin-setup/2.-configure-embed/sharing-level.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.