> For the complete documentation index, see [llms.txt](https://docs.ixhello.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ixhello.com/ixhc2/technical-specifications/flow-ownership-and-organization-sharing.md).

# Flow Ownership and Organization Sharing

The **Flows list page** now includes a new owner column that displays if an assistant is private or shared with the organization.  Individual owner information is coming soon.

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2F26ZC4xQJbhTuoeIS664K%2Fimage.png?alt=media&amp;token=fcfbd357-f3a5-41f5-8a76-b0fd086ca4b6" alt=""><figcaption></figcaption></figure>

#### Ownership Indicators

* If a flow is **owned by you**, you’ll see a o**rganization** **shared icon** next to "M**e**" under owner column.
* Organization‑owned flows are:
  * Visible to all users in the organization
  * Fully editable by any user who has access
* Flows Owned by you:
  * Personally owned by you
  * Can be only edited and accessed by you

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FSNLZjCUUJ99tg2yhoQL7%2Fimage.png?alt=media&amp;token=3b41e630-a43b-4534-916b-06f86022175c" alt=""><figcaption></figcaption></figure>

#### Changing Flow Ownership

1. Open the flow’s **Settings on an existing flow.**
2. Navigate to the **“Shared with organization”** option.
3. **Uncheck** the box to remove organization sharing and click 'Finish'

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2F5ZfSXI5gReaAXeC3WRp9%2Fimage.png?alt=media&amp;token=c53ffc79-4a4c-4f11-96f7-7be8044803fa" alt=""><figcaption></figcaption></figure>

When you uncheck this option:

* The **Owner** changes to **you**
* The **organization share icon disappears**
* The flow becomes **private**, visible and editable **only by you**

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FDhIPrKAwfULaJDIrnd8d%2Fimage.png?alt=media&amp;token=fc056dd9-3bad-42f5-9183-c14f2898725f" alt=""><figcaption></figcaption></figure>

If another user unchecks the same option on a flow they shared:

* The flow will no longer be visible to other users
* Only the new owner will retain access

***

### Consistent Behavior Across the Platform

This ownership and sharing model apply consistently across multiple areas:

#### Chat Widgets

* Chat widgets also display the **organization share icon**
* Widgets shared with the organization are visible and editable by all users

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FBAt2OBT8Max39a5UXrkm%2Fimage.png?alt=media&amp;token=205bcabd-e778-4a44-9ddb-e87ef5859cd0" alt=""><figcaption></figcaption></figure>

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FoZFHgxLWh9wV5RfgiMk8%2Fimage.png?alt=media&amp;token=e4b731b6-7d53-408c-acdd-690bbf2775f1" alt=""><figcaption></figcaption></figure>

When you haven't opted for Share with the organization option, then:

* The **Owner** changes to **you**
* The **organization share icon disappears**
* The flow becomes **private**, visible and editable **only by you**

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FAzVZLUNfYZHT10R1zwsq%2Fimage.png?alt=media&amp;token=af194115-0fea-4e8a-a57a-af577e4058c3" alt=""><figcaption></figcaption></figure>

#### Integrations (REST, MCP, Knowledge Base, etc.)

* Integrations now include an **Owner** column

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2FIIwgUG3rP8WnhgIlMl1L%2Fimage.png?alt=media&amp;token=3c60f5ac-f342-4757-a31a-2ddf36b50ef1" alt=""><figcaption></figcaption></figure>

* Selecting an integration and clicking **Edit** opens the settings panel
* You’ll see a **“Share with all”** checkbox
* Unchecking it makes the integration private and assigns ownership to you

<figure><img src="https://4187494610-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFe4cpY1jy0FJ4kgC7wSx%2Fuploads%2Fbs9AhHMFYSzDAToT0PXD%2Fimage.png?alt=media&amp;token=6fdcce6b-a940-400b-b01c-fab74a0d496d" alt=""><figcaption></figcaption></figure>

The clearly visible Owner column and shared icon make it easy to understand who owns a resource and whether it’s organization‑wide, while unified behavior across flows, chat widgets, and integrations delivers a predictable and intuitive experience for all users.


---

# 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.ixhello.com/ixhc2/technical-specifications/flow-ownership-and-organization-sharing.md?ask=<question>&goal=<user_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.
