Workspace DB / filemounts should narrow down the users' mounts
Currently there is only an option to add specific filemounts to the WS. This breaks all user/usergroup based filemount permissions.
So I suggest three options:
a) only WS filemounts
b) intersection of WS filemounts and user filemounts
c) only user filmounts
a) is the current state, b) is a meaningful extension that takes user filmounts into account but adds WS restrictions and c) is simply the state without any WS options which may come in handy.
(issue imported from #M4203)
#1 Updated by Andreas Wolf over 13 years ago
I would also add an option d) Combine workspace- and user-filemounts - so if you have filemounts A and B in the workspace and B and C in the user's options, the user would have access to A, B and C in the workspace.
The only problem arising could be that no filemounts can be set for the live-workspace, so you would have to add the filemounts to the user's options to have them in the live-workspace.
Edit: And I would also do something similar to this for the DB-mounts - as far as I know, their current behaviour is the same as with filemounts.
#3 Updated by Cedric Spindler almost 12 years ago
The current concept seems to be like this:
Every group has its own workspace and within the workspace the file and page mounts are defined. The file an page mounts of the group (user) itself is just recognized within the "live system".
The problem with this concept is, that you will get multiple workspaces for the same page if you have a more complex restrictive group setup.
Imagine you have the section "Solations" with a subsection "Open Source", Further you have users which have to access the whole solutions tree, and some users which should only see the "Open Source" tree.
You don't want to manage two workspaces for these sections (Solutions and Open Source) only for denying the Open Source guys to access the whole "Solution" tree, because there is a Section "Microsoft" within it ;-).
The concept should be like this:
The workspace should recognize the page and filemounts as well as the group and user permissions that are configured for the "live system". It would allow to simplify more complex restrictive group setup.
#4 Updated by Alexey Boriskin over 11 years ago
I have added the patch. Patch do the following.
At first, it saves default old behaviour if other is not explicitly set.
Then, it introduce new user TS Config option "options.folderTree.WSFilemountsMode".
That option can be one of 4 values:
1) ignoreUser. the same behaviour as before and as option is not set at all: user filemounts are ignored.
2) ignoreWS: new feature. In that case, workspace settings are ignored and filemounts come from user and group permissions.
3) combine: new feature. In that case, workspace filemounts are combined with user filemounts.
4) intersect: new feature. In that case, user have access only for those filemounts, that are selected in workspace settings AND also accessible for that user in user settings.
#6 Updated by Benni Mack about 9 years ago
According to the workspaces team, this feature will be implemented without an option:
This means, that selecting a filemount / db mount in a workspace will narrow down the existing list of a users' mount.