search

genouest / genouestaccountmanager

Account manager for core facility
GNU Affero General Public License v3.0
5 stars 8 forks source link

Maximum account number feature #30

Open OlivierCollin opened 5 years ago

OlivierCollin commented 5 years ago

We need a way to set a maximum number of accounts. When this limit is reached, the account management system should inform that no new account will be created (or that the account request is on a waiting list - to be discussed, but I guess that, if someone feels that an account needs an unforeseeable time to be created, he will ask to another facility). The interface has to give a way to set this limit according to the facility capabilities.

osallou commented 5 years ago

As admin actives (or not) users, why setting a hard limit? Admin can decide to reject demands

OlivierCollin commented 5 years ago

It is intended more for the users than for the admins. This limit is intended to provide more transparency to the user asking for an account. When a user wants to send a request for an account, it is much better to inform him/her that the maximum number of account has already been reached (and that his/her request will be rejected or put on a waiting list). The account creation form can be activated or inactivated according to this limit, allowing the user to search for another facility.

By the way, when an account request is rejected, is the user informed ?

osallou commented 5 years ago

user is not informed of rejection

so limit reached would be a message to inform user but registration would remain the same anyway?

mboudet commented 5 years ago

Might be easier to redirect the registration page to a warning, than to let an user go through the whole registration process.

OlivierCollin commented 5 years ago

I am not sure about the interface behaviour when the limit is reached:

The last option does not seems to be very transparent neither good for the user since he can not know how long it will take to see his request fulfilled.

mboudet commented 5 years ago

Do we want to to enforce the limit as 'hard' or 'soft'? Meaning, if a group of users working on the same project join, do we split it if the limit is reached?

osallou commented 5 years ago

disabling registration form would completly forbid his registration while we still may accept him for good reasons....

I would rather simply add on registration page a message informing that our "limit" is reached and that he may be not accepted or be on waiting list. Up to him to try to register anyway.

Registration is always accepted on our side, he may simply remain in "pending" accounts. Up to the administrator to activate him, or not.