We'd like the option to mark Inbox Flows as private, the same way Skills can be made private today. Right now any flow tied to a user's Skill is visible to everyone in the tenant, even when the Skill itself is meant for that person only.

Current behavior

When a team member builds a flow that's associated with their Skills, everyone else in the tenant can see it. You can't limit visibility to the person who built it or to a chosen group.

Requested behavior

A Private/Shared toggle on each Inbox Flow, matching how Skills work now.

Private flows are visible only to the owner and to admins.

If a Skill is set to private, any flow tied to it is private by default.

Optional: share a flow with specific users or groups instead of all or nothing.

Business impact

Less noise: The flows list gets cluttered with everyone's personal flows, so finding the ones that matter to you takes longer.

Focus and productivity: People spend time reviewing and second guessing flows that aren't theirs instead of working on their own queue and automations.

Ownership: Engineers should be able to build and test their own flows without them being picked apart before they're ready or meant to be shared.

Consistency: Skills already support private visibility. Flows that depend on those Skills should work the same way.

Priority: Medium to High. This affects day to day efficiency and team dynamics across our service desk.