[Daloradius-users] Disabling user accounts (and wishlist points!)

[Ian D. <ia...@aa...>]

Hi Liran,

I'm resending this as I just realised I didn't send it to the list, so
sorry about that!

Thanks for emailing back about my questions regarding disabling user
accounts, my apologies I didn't respond sooner, but I've been quite busy
while thinking greatly about this and what would be the easiest way to
achive disabling/enabling users.

In general we love the ease of the interface, (thank you very much!), and
it really is simple enough for anyone to use, but as to my earlier email
about the handling of the disable/enable users function, the inability to
assign a priority value to groups makes the disable function a bit onerous
as you have to manually change membership due to both groups having the
same
priority value anyway.

I've added a few things below that would be my wishlist ( I don't know if
any of them would break any RFC's?) for future Daloradius releases after
having used it for some time now:

User Accounting:
Allow Date Accounting to be set to a range, and keep that range instead of
resetting back to the current month. This is a recurring problem at the
start of every month when you need to check accounting records for several
services for the last few weeks.

System Configuration:
Ability to automatically schedule a backup from the GUI.

User Management:
Ability to set a default user group for new accounts.
One click disabling a user account moves the user into a disabled group,
doesn’t add an extra group.
One click enabling a user moves user back into default user group (feature
addition as above).
Currently it’s an issue for some people to understand how to get rid of
the extra groups added when enabling/disabling, and you have to manually
change the group anyway to enable.

Search Users:
Allows more search criteria, such as all disabled accounts, never logged
in, etc

System Configuration:
Create permission groups for new operators, grouping appropriate
permissions based on admin or support access required, for example
provisioning should have read access to most user related details, but
write access only to the portions of Daloradius that allow editing or
creating a user account. Similarly, NOC staff would have no need for any
billing related areas, except the ability to see if a modem has
authenticated, and be able to test the account, etc.

Again though Liran, great product, and it really does work well, I'm very
happy with it thank you.

regards from OZ, Ian