-
Notifications
You must be signed in to change notification settings - Fork 78
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
Admin approval #2
Comments
This function would be very nice. |
I just posted a $5 bounty on Bountysource! https://www.bountysource.com/issues/4144723-admin-approval |
Yes please! Admin approval would be a very desirable option!! |
This is a work in progress on branch |
What a I do as workaround is that all new users comes to the "new" group, from there I can manage which should I move to "real" users. The field with a full name would be good! |
Same as carlos but i set the storage limit to 1kb so nothing can be Op di 13 okt. 2015 01:49 schreef Carlos Damken notifications@github.com:
Met vriendelijke groet, E. Holm |
After discussions at ownCloud conf, decisions are made to change the registration flow, in order to be more straight-forward and simple. There are 2 alternatives to choose from: New registration flow A
But I guess user will likely forget his/her password by the time admin approves, so here's the alternate flow to prevent that. This flow is also less hacky, becasue flow A needs to write directly to ownCloud's user password. New registration flow B
@cdamken @tobiasnix What do you all think? |
Subtasks:
|
As there is a native password reset feature in owncloud i am voting for flow A. Its one step less for users who remember their password. |
Would also go for A although B seems workable. You could include the reset password link in the email maybe? Another option would be to add the password to the registration email, but I find it quite insecure when sites do that, never know for sure if someone's mail server is using ssl/tls. The workaround still works for me, user group validation has no apps, 1kb storage, they get the notification upon login that their storage is full. Only problem is that they have access to the file sharing, which can't be disabled for usergroups. Which in turn makes the validation group able to view registered users, of what I can think would be a not wanted problem for some OwnCloud hosts. Could you give me an update how? Regards |
I thought of a new simplified flow: On first form, user inputs:
Validation email is sent to the user, notification is sent to the admin.
|
A (less 'burocracy'). I agree with @tobiasnix . |
Can't find this feature (admin approve required) in the latest nextcloud, how to get it on? |
@georgygoshin It's still a work in progress. |
I'd also like this feature |
May I suggest that in the process of approval by admin, the registered users e-mail will automatically be added to the user database ?? currently that seems not the case... all users e-mail settings are empty... edit:
|
Are there any updates on this? |
Also interested! |
I'm working on it. But I'm currently really busy. |
I can help to test it, just let me know when you have some advances and I can help. |
I'm also interested in that feature. @lordmampf I can help you. I've just downloaded the code. |
@MarcelAlers Thanks for your pr on my fork ;) |
I am also interested in this feature... Thanks |
If you ask me this needs to be in before this is usable on the open web without workarounds like a group with no storage space! |
On the current implementation there is no way to view pending users that had not confirmed their email (other than the database) It would be nice if pending registration would be displayed on the config page... Thanks :) |
Can you create a new issue for that? |
Can we have a field where we can assign approval by specific groups such as "Help Desk" in our case so they can manage the account creation process not only the administrator? |
After user enters email (maybe additionally full name), a new pending entry is created, waiting for admin's approval.
After approval, verification email is sent, then the user could create account by clicking the link.
The text was updated successfully, but these errors were encountered: