Skip to content

Multi-user mode: v7 has no controls to share boards or workflows #9673

Closed

Description

@lstein

Summary

In multi-user mode, v7 has no controls for sharing boards or workflows. v6 had both:

  • Boards: right-clicking a board let its owner set visibility to Private, Shared (others can view), or Public (others can view; the owner keeps control of rename/archive/delete).
  • Workflows: a workflow's owner could mark it as shared (public), so it showed up in every user's workflow library as read-only.

In v7 the board context menu has no visibility options, and the workflow library has no sharing toggle. Boards and workflows a user creates in v7 stay private: only the owner and administrators can see them.

The backend still supports both. PATCH /boards/{id} accepts board_visibility, and workflow records carry is_public, which invokeai/app/api/routers/workflows.py checks for access. The gap is only in the webv2 UI.

Reproduction

  1. Start InvokeAI with multiuser: true and log in as a regular user.
  2. Right-click a board in the gallery. There is no visibility option.
  3. Open the workflow library or a saved workflow. There is no share/public toggle.
  4. Log in as a second regular user. None of the first user's boards or workflows appear.

Expected (v6 behaviour)

Owners can set board visibility and share workflows, as described in the multi-user user guide (Configuration → Multi-User Mode → User Guide, "Working with Your Content in Multi-User Mode").

Until this is fixed, the gap is listed on Troubleshooting → Known Bugs.

Activity

  1. added
    bugSomething isn't working
    frontendPRs that change frontend files
    on Oct 4, 2026
  2. JPPhoto commented on Oct 19, 2026

    @JPPhoto
    Collaborator

    @joshistoast Workflows aren't quite there yet in webv2 for multi-user setups:

    • The Workflow Library has no public/shared tab. Yours shows the current user’s workflows, and Browse shows defaults.
    • The Call Saved Workflow node’s dropdown includes public workflows from other users, mixed with other options, but only if they’re callable. So this behavior is correct!
    • There’s no frontend control/interface to make a user's workflow(s) public. The backend has an endpoint for changing visibility, but webv2 doesn’t call it.
    • The backend does not allow a non-owner to update a saved workflow even if it's set to public unless it's an admin doing the updating - that's probably correct behavior. But there's no frontend linkage for this.
  3. joshistoast commented on Oct 23, 2026

    @joshistoast
    Collaborator

    @lstein #9952 seems to resolve most of your points

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    7.0.0bugSomething isn't workingfrontendPRs that change frontend files

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions