For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Ownership Indicators

  • If a flow is owned by you, you’ll see a organization shared icon next to "Me" 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

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'

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

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

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

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

  • Integrations now include an Owner column

  • 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

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.

Last updated

Was this helpful?