Subusers about meta HOT 17 OPEN

Permissions:

General

• execute console commands
• view plugins
• add and remove plugins
• view file manager (maybe certain folders)
• change server plan
• purchase credits
• Manage roles/users
• Access backups
• Server settings (toggleable which features ur able to use)
• Danger zone (toggleable which features ur able to use)

Limitations

• "blocked" words or phrases for skript or whatnot
• Stop mass file deletion, i.e. if someone tries to delete a lot of files in a short amount of time stop that action
• Notify user actions on owner login
• See user actions on login

Notable stuff:

• protection mode, only allows users to have suggestion access similar to google docs where the owner can accept/reject stuff
• versions of the console files, like google docs
• add force 2fa
• Subusers need to have account liked with Minecraft to stop people with bad intentions
• This is PER SERVER

Possible prest ranks:

• Co-Owner:
  all permissions

• Network Admin
  all perms except:
  except for mass file deletion, add users, and see user actions on login

• Developer:
  see all files and edit certain files and use the console, as well as all member perms

• User:
  Read-only access to plugins and parts of file manager.

Please note that these are just my ideas, while nothing is set instone.

from meta.

Oh, I was thinking of a more luckperms based type thing, where you can do that type of stuff. Maybe "groups" is a better name for them instead of ranks. Premade ones would just be a template for people they can delete if they want. If you wanna have a lot of users managing a server, it may be easier to assign them a group instead of permission nodes for each thing. Of course, you can do personal permission nodes as well.

I also would really like to push the rollback and suggestion feature, because adding a feature as this may help prevent acc griefing and people crying in #support

from meta.

something like this could be cool, all checkboxes:

• Console Access [] send commands via the panel
• Server Settings [] settings tab + world tab + appearance tab minus send command unless console access is checked
• File Manager [] plugins folder blocked unless plugin management is checked
• Plugin Management [] manage plugins including manage plugins folder - if they don't have file manager perms they only have access to the plugins folder
• Danger Zone [] maybe another dropdown containing danger zone options?
• Backups []

items missing access could maybe be grayed out and when they hover it shows they don't have access?
I'm not sure exactly how credit spending would work

did you not see this lol: #13 (comment)

also just edited some of urs into mine + made it cleaner

from meta.

Let us know if you have other ideas for permissions or how we can best implement this! It's definitely planned, but not at the top of the list quite yet.

from meta.

Seems great, but make sure features are strict. If I get a developer, I want them to be able to add and change skript files, but not delete them, and if they grief the code, the audit log should be able to recover the code, kind of like Google Drive's edit audit log.

from meta.

Seems great, but make sure features are strict. If I get a developer, I want them to be able to add and change skript files, but not delete them, and if they grief the code, the audit log should be able to recover the code, kind of like Google Drive's edit audit log.

I mean if they can change files, they could also just make it an empty file which is as good as deleting.

And yes totally agree, would need to implement an audit log feature as well. Not sure if we could do full revision histories though and let you undo.

from meta.

I hadn't considered roles, how important do you think that is? My thought was to have a permission matrix, then you add a user and then select which permissions you want to give them.

from meta.

I hadn't considered roles, how important do you think that is? My thought was to have a permission matrix, then you add a user and then select which permissions you want to give them.

Let's not try to limit our features just for ease of access. There are also things on your permissions list, like how admin shouldn't be a higher role than developer.

from meta.

Users should be able to belong to multiple groups; permissions should be merged from top to bottom depending on group "priority"

from meta.

Thinking more like luckperms but better. You can delete the groups, make them bigger, and everything else. Reorder them, add perms, or just make your own perm system. The goal of that is to nube proof it as much as possible, but allow as much ease of access as possible. Oh, and what iGalixy said would just be done through group parents, and I wrote the perms from highest to lowest and I was being lazy lol.

from meta.

something like this could be cool, all checkboxes:

• Console Access [] send commands via the panel
• Server Settings [] settings tab + world tab + appearance tab minus send command unless console access is checked
• File Manager [] plugins folder blocked unless plugin management is checked
• Plugin Management [] manage plugins including manage plugins folder - if they don't have file manager perms they only have access to the plugins folder
• Danger Zone [] maybe another dropdown containing danger zone options?
• Backups []

items missing access could maybe be grayed out and when they hover it shows they don't have access?
I'm not sure exactly how credit spending would work

from meta.

Console:
- View [ ]: check to let user view console
- Send [ ]: send commands in console "view" must be checked
- Start [ ]: start the server, requires "view"
- Stop [ ]: stop the server
- Restart [ ]: restart the server

SubUsers:
- Create [ ] create subusers
- View [ ] view subusers list
- Update [ ] update subuser permissions NOT THEMSELF
- Delete [ ] remove subusers

File:
- Create [ ] create new files in the manager
- Read [ ] view files in the manager
- Content [ ] read the content of a file
- Modify [ ] modify the content of a file
- Delete [ ] delete files from the manager
- Archive [ ] create file archives
- SFTP [ ] allow FTP access to files

Backups:
- Create [ ] create a new backup
- Replace [ ] replace a previous backup
- Delete [ ] delete a backup
- Download [ ] download a backup
- Restore [ ] restore a backup

WHEN ALLOCATING PORTS ALLOWED (if ever)
Allocations:
- Read [ ] view allocated ports
- Create [ ] allocate a new port
- Remove [ ] remove a old port

WHEN AUDIT LOG IS ADDED
Logs:
- See [ ] see the auditlogs

WHEN DATABASES GET ADDED
Databases:
- Create [ ] create new database
- Read [ ] view databases
- View Password [ ] view the password
- Delete [ ] delete a database

Danger:
- Rename [ ] rename the server
- Delete [ ] delete the server
- Reset [ ] reset the server

from meta.

I hadn't considered roles, how important do you think that is? My thought was to have a permission matrix, then you add a user and then select which permissions you want to give them.

I know that this thread has been dead for a while but, what if there was a permission matrix and you could select a template to modify if you would like. It would make it both simple while also allowing lots of customization.

from meta.

over 3 years! bump

from meta.

I really recommend this, this might be useful for users who don't want to share their personal accounts and just want access to the Minehut Server. If this every comes I think adding permissions for them is also useful

To me it's a 👍🏻

from meta.

bump

from meta.

from meta.