How do you handle explaining to clients how the username & email logins work in Cloudron?
I'm wondering how you may explain to your clients how the username and email logins work / interact with each other. I find myself explaining this to clients often and they forget by the time they need to login again / reset their password / access a different mailbox, etc. Trying to find a way to properly document this for my clients in a way that's perhaps more understandable than what I've been doing.
- Most of my clients only use email on Cloudron, they don't use their Cloudron username since they don't need to access anything else.
- Since Cloudron can have one user "own" multiple different mailboxes, users need to use the mailbox email address as the username so the Cloudron server knows what mailbox they want to see at that time, and they use the password associated with their own user account.
- This confuses some users because they are used to logging into other services online with their email address and password, and recognizing that as the "account", rather than in Cloudron where they can have multiple emails to the same "account". In other words, the concept of an online account as we know it doesn't quite jive with their own understanding of how online accounts work. And not many are too technical so they don't quite get it.
This causes a bit of confusion for example when I'm asked to reset a password for a mailbox, because I have to explain that I can reset the user password attached to that mailbox but that doing so will reset it for all mailboxes that are owned by the same user account. So I need to get their confirmation that they want me to still proceed, or otherwise we correct the credentials they were using to login with.
So I was wondering if there was any way you guys have come up with to better explain how this works to clients. Figured someone's maybe found a good way to explain this to their users in an understandable concept that's easy to remember. Any ideas or suggestions?
luckow last edited by
What is the use case? Webmail or Clients like Thunderbird?
True - webmail is a bit confusing when you switch through different mail addresses. But Thunderbird? Setup & forget
Since Cloudron v. 5.x (I forgot the number) the possibility to have aliases from different domains helps me (my use case) a lot.
d19dotca last edited by d19dotca
@luckow Good question!
For me, most of my clients using email heavily are medical clinics - in fact their use has skyrocketed probably 400% since they started doing COVID-19 testing (which is why I'm eagerly awaiting being able to off-box their mail storage, because I'll be running out of space in a maybe 6 months because of how quickly they're consuming space now with all these copies of forms and such).
Apart from managers mostly, they use webmail. The managers mostly use a mix of webmail and client applications, but the staff pretty much exclusively use webmail. Mostly because the staff don't need to check emails outside of business hours, and they also jump around to different workstations constantly because of the nature of their job, so having Thunderbird setup on all of them for example won't work too well since some people are not allowed access to certain mailboxes, etc.
I think you're right, that's part of the problem in a way, as it's confusing to explain how user accounts work and mailboxes when they're constantly signing in with the mailbox they need using webmail, that probably exaggerates the problem for them to some degree.
Any suggestions? I don't think I can see a client application helping in this case, it'd just be too complicated to setup for all of their needs with so much hopping around workstations.
Roundcube seems to support login with either email or username. TBH I wouldn't use any of the other webmail alternatives here anyway. Does that help?
@marcusquinn I don't think it works that way on Cloudron though because of the Cloudron configurations for multiple mailboxes to a single user. If I try to login with my Cloudron credentials in Roundcube, it fails to authenticate. It'll only work if I use my Cloudron mailbox for the username. Does it actually work for you that way? It's an interesting point though... I wonder long-term if Cloudron somehow could automatically setup Roundcube to link to each mailbox the user is an owner of, that'd be pretty useful and may take away some of the confusion, although it could create different confusion too. haha.
@marcusquinn Interesting, that's definitely not how it works for me. Even in Cloudron's own documentation, it seems like they need to login with the email address, though it mentions "multiple domains" so maybe that's a difference between our environments. Ref: https://cloudron.io/documentation/apps/roundcube/#multi-domain-setup, and https://cloudron.io/documentation/email/#email-client-configuration suggests that it should be the email address as the username too for any client app setups. So that's very strange, haha. But hey that'd be awesome if I can get it to work with usernames instead of email addresses, that'd likely remove some of the confusion with my clients.
@d19dotca I might not be understanding fully, but I have a few clients for whom I anticipated this sort of challenge - managing/using a cloudron name plus email login info. So here is what I did. I made groups and assigned their cloudron username to their respective group, and then restricted app access on the cloudron to the only one they need - the SOGo installation. BUT, I never told them about this! All I gave them was the SOGo url and their email login info. But they also just have one email account, so none of them need to sign into more than one webmail account or setup more than one email client.
I was unaware of the usefulness of the User and Group options in Cloudron until I was setting up Wordpress for someone and wondered how to manage it. So rather than letting wordpress amange, I made them a Cloudron user and set that to work with their wordpress install. Then they needed another app, and I realized I could then make a Group, add them and myself, and restrict access to the apps in question, and then I could still take advantage of the Cloudron management. Without Cloudron Users and Groups I'd be busy chasing down individuals credentials over several apps! Could this be of help to you?
@d19dotca Just a quick note that I tried this at sogo.example.com and I could only login with the email and password, not my Cloudron username + password. But I wonder if this is because my Cloudron user has several different accounts on the Cloudron, and thus different emails, so SOGo (in my case) needs more specific login info?
Generally the email web clients are setup on Cloudron just like a desktop client. The login should be email+password since a username may have more than one address associated. In the past username+password worked well since there was a direct mapping to
email@example.com as an email address, but we have moved away from that long time ago.
Some webmailers do support managing more email accounts within one login session, but that since support for that is not unified, this adds to the confusion for the user.
On top of that, rainloop for example would allow username+password in case that user owns the
firstname.lastname@example.org rainloop would append the domain automatically, while the input field in the login screen actually indicates that one should enter a full email address.
While some combinations currently work due to app specific quirks, the general flow should be to always user email+password for a user.
@nebulon Perfect, so that confirms what I suspected that it requires email@example.com for the username when using webmail. No idea why this works for @marcusquinn but maybe that's from the older mappings you mentioned that existed a "long time ago".
Any thoughts on how I can improve users understanding of how a user account relates to mailboxes? I know we're all technical people so it seem obvious to us, but many people are not that technical and I'm trying to find a way to help those ones who are repeatedly confused by the relationship between a user account and a mailbox, when they never have to use their username for anything really since they're only ever using webmail.
Do you think there's a way Cloudron can improve this a bit? Because I liked one suggestion above which was the ability for users to login to webmail with their username instead of the mailbox, and then Roundcube for example is auto-configured to load up all the mailboxes the user currently owns.
@d19dotca Documentation is unclear.
With roundcube you can user the username is the email suffix is the same as the domain as the webmail.
Just checked, I only use username for login.
@will Ah that's an interesting workflow. According to the Cloudron developers though, if I understand correctly, we should be using our full emails to login with, not usernames. Nebulon wrote "While some combinations currently work due to app specific quirks, the general flow should be to always user email+password for a user."
Since I'm managing over a dozen clients freelance, I think I need to stick with the "official" recommendations whenever possible just to avoid possible future issues / breaks to the workflow in the future. Although maybe this is a safe one to go a different route on. Interesting observations - until this thread I had no idea some users are logging in with their usernames for webmail. I can't even do that, but I guess that's because of the domain setup for it, perhaps.
If usernames could be edited, I guess you could set them all to be their email address as well?
@d19dotca Please note that login with email address is for web mail clients like rainloop/roundcube. Most non email client apps are using the username!
We are aware of the potential confusion, but unless upstream apps can agree on one way or the other is is hard to make that uniform.
@nebulon Ah, interesting. So because of how the Cloudron documentation is, I've used full email address for even desktop and mobile clients. Are you saying that we should be using usernames for that instead of email address for desktop clients as a best practice?
d19dotca last edited by d19dotca
@scooke Ah yes, I heavily use groups already, basically one group per freelance client/business, and all users of that business are in that group. But this unfortunately is all back-end mechanics, it doesn't change the front-end for users at all.
I probably wouldn't have this difficulty with having to explain (and repeatedly) how users/accounts related to mailboxes and such if my clients all used other apps too like signing into their Wordpress site because then they'd be actively using their user account itself and likely then understand better how it relates to their mailboxes, but many of them only use webmail because they only have a website and email and never need (nor care) to login to the website side of things. I think that's why it seems I'm one of surprisingly few people who seem to have experience this difficulty with clients with trying to get them to grasp how user accounts relate to mailboxes when they have so many mailboxes each.
@d19dotca To clarify, email webapps or desktop apps should use the email address.
For other apps on Cloudron, one should use the username if that is supported by the app.
@d19dotca You could present this as the way of the future then! Rather than it coming across as a new hassle to their established workflow (not saying that is what you are communicating), you could tell them this is the future, now, this is how things get done, that they are privileged to be using Cloudron, and since this is how Cloudron works, then they have a wonderful chance to broaden their minds and processes!
@nebulon ah okay, so yes that’s how everything is being done already then.