Per domain user subscription and admin role
-
@avatar1024 also as @marcusquinn suggested, I don't see why assigning new users to domains vs assigning them to groups is in any way more error prone. The only difference is that apps installed have to be setup with the correct groups.
-
replied to nebulon on last edited by
@nebulon for me it isn't about error proneness, it's simply a matter of being able to quickly and easily create and apply domain-based groups.
i.e. right now it is perfectly possible to a create a group and call it somedomain.com and then to manually limit any app on that domain to that group, it just takes lots of steps.
I'd be great (i.e. much quicker and easier) to be able to just say "limited all apps on x domain to x group".
-
replied to jdaviescoates on last edited by
@jdaviescoates Yep, this would be really useful. I have some friends who want to host their website on my site but I don't want to give them full admin roles.
-
replied to cyberfreakde on last edited by
@cyberfreakde you can already do it using the existing groups and roles, you just have to remember to do it for each app
-
@cyberfreakde Right, as @jdaviescoates set, just create a "website" group with just the users and then set the group as the permission in the app's Access control view. The important thing to remember is that the "default" Access is accessible to all. So you have to go into each app and make sure it's not accessible to all. Another thing is that Cloudron "admin" always has access to all apps.
-
@cyberfreakde Yes, in Cloudron 6, there is an option - https://docs.cloudron.io/apps/#non-admin-access . The SFTP access info is not displayed for normal users currently (which can be considered a bug). But they should be able to login with
username@app.domain.com
and their cloudron password (sftp port 222). -
replied to jdaviescoates on last edited by
@jdaviescoates @cyberfreakde
you can also set up a WP instance with all the groups configured as you need them, then just clone it for new sites and drop in users as needed. Config once, clone many. -
replied to jdaviescoates on last edited by
@jdaviescoates Yeah, for that we need a group dropdown to select all the different apps.
-
replied to robi on last edited by jdaviescoates
I'm not sure why this has been marked as solved. Aside from all the groups stuff I'd still really like to be able to make people admins for a specific domain.
Like, right now I'm working with @thetomester13 on selfhost.cloud stuff and whilst I've created a related group and given him access to relevant apps, I can't add him as an admin because then he'd have access to all my other stuff too.
But it'd be really handy if he were an admin for all selfhost.cloud stuff so he doesn't have to ask me to restart apps, increase memory for apps etc etc.
-
replied to jdaviescoates on last edited by
@jdaviescoates Maybe group admins would be easier to do.
-
I've asked for that a few times over the years: I would image a group-admin role for a user (who can have one or multiple domains). That group-admin can do all the stuff a regular admin can do, but only for the domains they're assigned to.
A second request was something like a user/app limit per domain (set by the superadmin), so that the group-admin and/or group-manager couldn't add more than 5/10/xx people/apps, so they don't trash the place and keep their resources in check.
This scenario would be for bigger servers that host multiple tenants which shouldn't see the stuff of the other users but can still operate independently.
-
Erm, separate Cloudron instances perhaps?
-
replied to marcusquinn on last edited by
@marcusquinn yeah, that's probably what we'll end up doing. Just trying to bootstrap and avoid the cost of another VPS even though Hetzner are so affordable (I've got so many credits for referring people that the cost of another Cloudron sub isn't an issue right now, although of course often that'd be more than the VPS itself)