1. Proposed title of this feature request

• Advanced control of  maxNumberOfRunningWorkspaces and maxNumberOfWorkspaces

2. What is the nature and description of the request?
Currently, it is only possible to configure 'maxNumberOfRunningWorkspacesPerUser' and 'maxNumberOfWorkspacesPerUser' globally for all users in the CheCluster/devspaces. However, there is a need to define different values for these parameters for different users/groups.

3. Why does the customer need this?
Some developers and architects are requesting the ability to use more than one workspace at a time. They would like to restrict this capability to certain roles, allowing only specific roles to spin up multiple workspaces.

4. How would the customer like to achieve this? 

• Role-based permissions for opening multiple workspaces at once
• Default value for maxNumberOfRunningWorkspaces and maxNumberOfWorkspaces
• List of users/groups with a different values for maxNumberOfRunningWorkspaces and maxNumberOfWorkspaces

5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
The scenario is straightforward: testing different values for different users/groups and ensuring that only the specified number of workspaces can be opened or run simultaneously.

6. Is there an existing RFE upstream or in Red Hat Bugzilla?
n/a

7. Does the customer have any specific timeline dependencies and which release would they like to target?
(will be available later)

8. Is the sales team involved in this request, and do they have any additional input?
n/a

9. List any affected packages or components.
CheCluster/devspaces

10. Can the customer assist in testing this functionality if implemented?
(will be available later)

11. Define the value or impact to you or the business: 
The context switching between projects can introduce overhead, especially for senior developers who frequently switch between projects. Additionally, with more advanced workspace configurations, there may be conflicts with port-forwarding settings if using an all-encompassing meta-workspace.