Application Deployment - New instance, new permissions required for same Game

[Jeremy_Roath]

System Information

Field	Value
Operating System	Windows - Windows 10 Pro on x86_64
Product	AMPService ‘Phobos’ v2.6.0.0 (Mainline)
Virtualization	None
Application	Application Deployment
Module	ADSModule
Running in Container	No
Current State	Indeterminate

Task

Creating Users and Roles

Problem Description

Issue

The issue I am having right now is the lack of reusability. I can set up a role to create an instance and start, stop instances. But what I need is to allow a role, to have permission to ONLY create a SPECIFIC server type, say Valheim and/or Minecraft. But I don’t want them to create any other type of server. Then, for each of those that they create, they automatically get permissions to manage the instance completely, or to the extent that I want them to.

It would be good too, if I said, okay, this Role can ALWAYS have this set of permissions any time a new instance of Core Keepers is made.

I have 3 kids, and I don’t want them to just go in reeking havoc on my server, but I also don’t want to have to keep changing permissions every time they decided to start their server over.

I’m sure there are a LOT of others that feel the permission system can use a LOT of work. I haven’t even really got this fully set up to use for my kids and I regret paying for it. I hope we are looking at more features very soon.

Reproduction Steps

• create user
• add permissions
• create role
• add permissions to the role to manage Minecraft
• create a new instance
• The role created can create instances, and manage one instance, but when they create a new instance, they can’t manage it. if I give access to manage any server, then they can change way too many settings within that most people shouldn’t have access too.

[ThePotatoKing]

• The Advanced edition has Template Roles which can apply the same permissions across multiple instances of the same type.
• Automatic userperms-to-instance assignment is an Enterprise-only feature.
  • You can accomplish similar results by allowing the users to access all instances, then explicitly deny access to ones you don’t want them to access (that way they can access any newly-created instances without your intervention)
• The permissions system does need some work I do agree, but it can accomplish your goals in it’s current state, feel free to join the discord if you ever need to hash out some weird permissions issues, there’s usually someone around.