You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue:
When you create an admin mount point, all admins get this mount point assigned by default what means, it appears in the web-ui and is propagated to the client.
Feature Request:
The admin mount point is created in the same way, but no user or group even not the admins get the default assignment. It is unassigned. This means, that this admin mount point does not appear on any users web-ui or client. This changes if the admin assigns this mount point to users or groups, then it behaves like usual. When removing all users or groups, this mount point becomes unassigned again.
Benefit:
Admins can prepare mount points in advance without unintentionally showing that mount point on any web-ui or client.
Note:
There is imho no change on the web-ui necessary, only on the backend. One possible exception, the current assignment text for admin mount points must change from All users to Unassigned.
GitMate.io thinks the contributor most likely able to help you is @PVince81.
Possibly related issues are #12530 (Feature Request), #8569 (Feature requests), #15818 (admin should not be able to select ldap groups for users), #7117 ([Feature Request] - In Admin user page), and #7118 ([Feature Request] Admin User page).
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions.
10.0.9
Issue:
When you create an admin mount point, all admins get this mount point assigned by default what means, it appears in the web-ui and is propagated to the client.
Feature Request:
The admin mount point is created in the same way, but no user or group even not the admins get the default assignment. It is unassigned. This means, that this admin mount point does not appear on any users web-ui or client. This changes if the admin assigns this mount point to users or groups, then it behaves like usual. When removing all users or groups, this mount point becomes unassigned again.
Benefit:
Admins can prepare mount points in advance without unintentionally showing that mount point on any web-ui or client.
Note:
There is imho no change on the web-ui necessary, only on the backend. One possible exception, the current assignment text for admin mount points must change from
All users
toUnassigned
.@PVince81 @DeepDiver1975
The text was updated successfully, but these errors were encountered: