Feature description

I plan to use nebi on a platform where there will be many users from a variety of teams I work with. I'd like the ability to:

• put nebi users into groups
• specify/organize environments by group
  • there are a lot of open questions here:
    • are users given different roles in each group (e.g. viewer/editor/admin?)
    • when I create an environment, does it live outside of the "groups" and then I just give access to that environment to the groups that need it or do I create the environment in the group?
    • how/where are groups created? Do all users have this power?
    • how does naming work? e.g. from the cli it would be nice if I just did nebi activate myenv and that would simply work without specifying the group, but if myenv happens to exist in 2 groups, then the CLI would ask me to specify the group via a group flag, --group mygroup.
• integrate groups with keycloak user groups
• organize the UI to view environments by group subsections (once I have 100 environments, this will greatly help me with organizing/finding things)

Value and/or benefit

• Enabling groups on the platform will enhance admin control (group A has edit access to all environments in group A vs manually giving each member of the team access to each environment).
• Enables grouping via the UI which will enhance visual organization of the page

Anything else?

No response