I already thought about an improvement of the idea. We mainly have 3 default roles right now:
- superadmin (can do everything) - administrator (can manage most of the objects of their org) - operator (limited permissions, usually a collaborator of a company or volunteer of a no-profit who help out with specific operations) I mostly test with superadmin and lately while testing with administrator and operator I've found many issues. We could have the procedure automatically create these 3 roles for every openwisp module which is also a django project and makes use of openwisp-users, eg: - find out if it's a django project (has the file tests/manage.py or tests/openwisp2/manage.py), if not, stop this operation - create superuser, eg: superadmin/superadmin (if it doesn't exist yet) - if there's a group (as django.contrib.auth.models.Group), create a staff user which is named after the group, all lowercase, so if the group is named "Operator", the user will be called "operator" (a small exception that in case the result is "administrator", abbreviate that to "admin", once the user is created, assign it to the default organization. The operation should be skipped if user already exists This way we'll have the 3 roles created automatically for each project which we work on and we'll be able to test much faster. -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/036d4be9-e1c4-4e10-87c7-4f1df4935414%40googlegroups.com.
