Add a "Shared with me" filter to the workflow list (Community Edition)

Feature Requests UI
1

Add a “Shared with me” filter to the workflow list (Community Edition)

Describe the problem

In self-hosted Community Edition, when another user shares a workflow with me, there is no way to filter the workflow list to show only those shared workflows.

Current behavior in the Workflows view:

  • Overview shows everything I have access to (mine + shared with me) mixed together.

  • Personal shows only the workflows I own.

  • The filter panel only exposes Tags and Status (Active / Inactive).

There is no owner != me, shared with me, or equivalent filter. As soon as a user has more than a handful of workflows shared from teammates, the Overview becomes hard to navigate because there is no way to separate “what I own” from “what others shared with me”.

The information already exists in the database (shared_workflow.role, homeProject vs. the user’s personal project), and the internal /rest/workflows endpoint already returns homeProject and sharedWithProjects per workflow, so the data needed for this filter is already there — it just is not surfaced in the UI.

Why Projects is not a workaround for Community users

The recommended pattern of organizing shared workflows into Projects is gated behind paid plans. Community Edition users still have access to per-workflow sharing between users (the Share button works, owners can grant editor/viewer roles), but they have no way to filter or group the result. So sharing exists, but discoverability of shared items does not.

Describe the solution you’d like

Add an Owner (or Shared with me) filter to the workflow list filter panel, available in Community Edition, with at minimum these options:

  • Owned by me — workflows where the current user has the workflow:owner role.

  • Shared with me — workflows the current user can access but does not own.

  • Any (default) — current behavior.

Optionally, allow filtering by a specific owner (dropdown of users who have shared something with me), similar to how Tags filtering works today.

A small badge or column showing the owner’s name/email next to each workflow in Overview would also help, so users can see at a glance which workflows are theirs vs. shared.

Describe alternatives you’ve considered

  • Tag convention (e.g. tagging every shared workflow with shared): works but relies on every user remembering to tag manually, and breaks as soon as someone forgets.

  • Direct DB query against shared_workflow joined with project_relation and user: works for admins with DB access, but is not viable for regular users.

  • Bookmarklet hitting /rest/workflows and filtering client-side by homeProject: works as a personal hack but is not a real solution.

None of these match the simplicity of a built-in filter, and all of them require either discipline or technical access that average users won’t have.

Additional context

  • Edition: Community (self-hosted)

  • Affected view: /home/workflows (Overview)

  • Existing filters in UI: Tags, Status — both already support the same UX pattern this request would fit into.

  • Data already available server-side: homeProject, sharedWithProjects, scopes returned by /rest/workflows.

This is a small UI addition that would significantly improve daily navigation for any Community team where users share workflows with each other.