Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Admin mount points should not have a default user or group assigned when ceated #32267

Closed
mmattel opened this issue Aug 7, 2018 · 2 comments

Comments

@mmattel
Copy link
Contributor

mmattel commented Aug 7, 2018

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 to Unassigned.

@PVince81 @DeepDiver1975

@ownclouders
Copy link
Contributor

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).

@stale
Copy link

stale bot commented Sep 20, 2021

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.

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

No branches or pull requests

4 participants