I have a potential project for a museum that needs some specific user manangement and I am not so sure on how to accomplish this.
groups of children and a teacher will recieve a user so they can together create a page and some subpages, upload images, etc. for this I would create a frontend login area and this user type will not have panel access.
the museum employees will have a few regular panel accounts that can create the users I mentioned above. after they create a user they can send the login info to the teacher so they can work on their stuff.
since it is a group, one of the requirements is that these frontend users don’t use email addresses but rather usernames. sure, the teacher could use her/his email or something, but that is the description of what they want.
I was testing a simple workflow today: I created a new type of user and the simple frontend login with help from the cookbook recipes and all works great.
the issue is though that I am using email addresses. when an admin creates a new frontend user in the panel, the email field is a requirement. again, here I could tell the client, you can use your domain, like @client.com and just give them some ID as an address, like email@example.com. but it seems like a counterintuitive thing to do for an institution to use random email addresses that each employee would have to choose.
also, for loging in in the frontend, the email and password are checked and it would have to be username and password instead.
is there a cleaner solution for this? optimally it would look like:
- museum employee starts new frontend user creation in the panel
- in the modal that opens the email is not asked nor required, but rather an automatic generated ID that is unique is already prefilled (meaning it would have to check if the ID already exists, or maybe just generate it from a timestamp or something)
- in the frontend the teacher logs in with the username and password
that way no email address is stored nor needed for the school group.
also, the frontend accounts must have a time to live. so the museum employee would create the user and give it 10 days or soemthing. after that, the login should not work anymore. I havent looked into this yet but maybe someone has a nice clean suggestion as well my first idea was something like an automatic change of roles from
frontenduserdisabled that happens after the time has elapsed. that way the employees can quickly see in the panel which users are already inactive. what would you suggest?
thank you all in advance!