Use case or problem
When symlinking config files around (so as to keep settings the same across multiple vaults) there aren’t usually problems, because if I change a setting in one vault, I want the other vault to have that setting changed as well. There is one problem though: the workspace file. Each vault is competing over the single workspace file.
Proposed solution
Create a setting, just like the ‘override config folder’ setting
where you can set the name of the workspace file for that vault (but not others using the same config folder).
This setting would have to be stored in the local appdata rather than inside the config folder, lest vaults using the same config folder fight over that settings file instead of the workspace file.