Issue Bug Needs Feedback Quiet

#107915Workspace switching bridged to all sessions of the current user

Ayke Halder 10/29/25, 17:11 updated 10/18/26, 13:08

Description

The workspace is stored in the “backend user data” – and not in the users “session data”.

Thereby workspace switches are completely bridged between all sessions of the same user!
Without any visual hint, that the workspace changed.

User logs in with two different Webbrowsers – e.g. Chrome and Firefox:

  1. User switches to Workspace-Foo in Chrome
  2. User switches to Workspace-LIVE in Firefox
  3. User creates new content element in Chrome – showing Workspace-Foo – but stores (unknown to the user) in Workspace-LIVE

User-A and User-B share the same account: User-A logs in on PC-A and User-B logs in on PC-B

  1. User-A on PC-A switches to Workspace-Foo
  2. User-B on PC-B switches to Workspace-LIVE
  3. User-A on PC-A creates new content element – showing Workspace-Foo – but stores (unknown to User-A) in Workspace-LIVE

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[BUGFIX] Workspace switching bridged to all sessions of the current user Resolves: #107915 Releases: main

History 3

  1. Ayke Halder changed subject Workspace changes bridged to all sessions of the current user Workspace switching bridged to all sessions of the current user <span data-processor="relativetime" data-value="2025-10-29T17:30:56+00:00" > 10/29/25, 17:30 </span>

  2. Benni Mack commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-10-18T13:08:54+00:00" > 10/18/26, 13:08 </span>

    we won’t support Option B from Core, that is because we should not officially support any account sharing functionality by design.

    Option A could be valid, and can only be solved by explicitly handing over Workspace ID on every request. tbh, this feels like a rewrite of the backend, or do you see it differently?