Hiding superadmin to deliver 'managed' cloudron to clients.

[micmc]

With the "superadmin" feature now part of CR features, it would be great if the "superadmin" user would be hidden from all other users, including any "admin" user.

Why?

That would allow MSPs to create CR instances and register oneself as the "superadmin", then create an admin account in CR to deliver the client as turnkey solution with fully installed CR with its domain name, hassle free ready to start to operate for less techie or much busy clients.

I believe that would open many possibilities that were not thought before as also the new cloudron.io's instance registration flow UI allows one to register multiple instances under one account now.

Thoughts and other ideas and suggestions are pretty much welcome.

[jdaviescoates]

@micmc said in Hiding superadmin to deliver 'managed' cloudron to clients.:

That would allow MSPs to create CR instances and register oneself as the "superadmin", then create an admin account in CR to deliver the client as turnkey solution with fully installed CR with its domain name, hassle free ready to start to operate for less techie or much busy clients.

You don't actually need to hide the superadmin (Owner in Cloudron-speak) to do that though, do you?

I mean, what's stopping you doing that anyway? You/ the MSP (whatever that is?) be the Cloudron Owner, the client is the Admin.

What am I missing? Why/ what benefit do you get from hiding the "Owner"?

More on Cloudron roles here:
https://docs.cloudron.io/user-management/#roles

[girish]

@jdaviescoates said in Hiding superadmin to deliver 'managed' cloudron to clients.:

What am I missing? Why/ what benefit do you get from hiding the "Owner"?

Maybe he means to hide the owner from inside apps and not in the Cloudron User listing as such? For example, may not want it to appear inside nextcloud when a user is trying to share a document and the owner name appears in auto-complete.

[jdaviescoates]

@girish in which case I'd just use a brand or business name for the Owner name and a generic email

[micmc]

@jdaviescoates said in Hiding superadmin to deliver 'managed' cloudron to clients.:

You don't actually need to hide the superadmin (Owner in Cloudron-speak) to do that though, do you?

I mean, what's stopping you doing that anyway? You/ the MSP (whatever that is?) be the Cloudron Owner, the client is the Admin.

What am I missing? Why/ what benefit do you get from hiding the "Owner"?

More on Cloudron roles here:
https://docs.cloudron.io/user-management/#roles

You have missed my point, that is what you are missing . I'm not asking how the roles work, nor if I can or cannot do that. I perfectly know that it can be done, and whether we can hide or not the superadmin - "owner", all I'm asking is for a feature loll

I guess, we're not all from the same background nor all MSP or Hosting provider, or whatever. One thing I know is I'm in the hosting industry and consulting and marketing online for more than 20 years and things like cpanel did not even exists when I owned and managed my first hosting servers. And as such, in this field there are MANY different markets and as much different approach to reach them with all kinds of offers.

Hiding the superuser is not an absolute, I think it would even be better if we have the choice, as provider, to hide it or not so the most can be happy. But, for the main market I target that would be a great feature as in, it would be better.

For comparison, or analogy, when I started to use cpanel to manage hosting servers for clients, installing this on a dedicated to serve cpanel to clients the top layer to full control over all clients is web host manager (WHM) and there was no layer above this. Through WHM we're creating cPanel accounts for clients so they have full control over their own hosting needs, however clients did not know, let alone see, that there was a WHM layer above its cpanel account and there's good reasons for that and one of them is I would not feel in full control and owning if I managed my server and apps and etc. while constantly viewer a "superadmin" (who is this?...) above me on my server. What I suggest is no more nor less than acting and seeing "superadmin" a bit as WHM and admin as cPanel user. It's an example to show the idea as they're not much comparable in reality. And through WHM we were also able to help and provide higher level support to cpanel clients all transparently.

Most of the technical details the business end user client don't bother nor even want to hear about, but having full control, security and privacy are very strong point of sale in most of my target audience. Hence, having the impression of being at the top of everything is very important for them.

Hope that helps better understand the idea.

[micmc]

@jdaviescoates said in Hiding superadmin to deliver 'managed' cloudron to clients.:

@girish in which case I'd just use a brand or business name for the Owner name and a generic email

That's what can be done already and that might be good for you and your target market, and that's fine. That's why also it should be then optional to hide or not the "superadmin" on the CR instance.

We should also keep in mind the CR "admin" "owner" can also use its own instance as an MSP itself very easily so that market can be very HUGE if one knows how to do marketing online.

[micmc]

@girish said in Hiding superadmin to deliver 'managed' cloudron to clients.:

@jdaviescoates said in Hiding superadmin to deliver 'managed' cloudron to clients.:

What am I missing? Why/ what benefit do you get from hiding the "Owner"?

Maybe he means to hide the owner from inside apps and not in the Cloudron User listing as such? For example, may not want it to appear inside nextcloud when a user is trying to share a document and the owner name appears in auto-complete.

And I guess, that is what would or should happen if we choose to hide the owner. I haven't thought really about this one but yeah, well thought and that should the be case also indeed, the superuser would not be seen in apps as well.

[girish]

@micmc said in Hiding superadmin to deliver 'managed' cloudron to clients.:

And I guess, that is what would or should happen if we choose to hide the owner. I haven't thought really about this one but yeah, well thought and that should the be case also indeed, the superuser would not be seen in apps as well.

We had this idea of creating a "service account" - https://git.cloudron.io/cloudron/box/-/issues/771 (which is scheduled for 7.3). I think this will get you this feature.

[micmc]

@girish said in Hiding superadmin to deliver 'managed' cloudron to clients.:

@micmc said in Hiding superadmin to deliver 'managed' cloudron to clients.:

And I guess, that is what would or should happen if we choose to hide the owner. I haven't thought really about this one but yeah, well thought and that should the be case also indeed, the superuser would not be seen in apps as well.

We had this idea of creating a "service account" - https://git.cloudron.io/cloudron/box/-/issues/771 (which is scheduled for 7.3). I think this will get you this feature.

This is how we see how great minds encounter!

Also, there's the discussion about the "email admin" role to which your issue above refers too as well, which several of us have followed as well, which have popped several ideas and views as well and has brought to the creation of such feature.