Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Team Member Permissions #2276

Open
vishalkadam47 opened this issue May 23, 2024 · 0 comments
Open

[Bug]: Team Member Permissions #2276

vishalkadam47 opened this issue May 23, 2024 · 0 comments

Comments

@vishalkadam47
Copy link

vishalkadam47 commented May 23, 2024

Description

The current permission structure for team grants the same level of deletion authority to all team members, irrespective of their role (owner, admin, or regular member). This means that any team member has the authority to delete any deployed service or project, regardless of who created it.

Minimal Reproduction (if possible, example repository)

Proposed Permission Structure:

Owner:

  • Has full access to manage all services and projects.
  • Can create, edit, delete, deploy, and view all projects.
  • Deployed services and projects remain hidden by default until explicitly exposed by the owner.
    Admin:
  • Can manage and delete services and projects created by members, but not those created by the owner.
    Member:
  • Can only delete their own deployments.
  • Can view and collaborate on assigned projects.

Bonus: Consider a "User" role for a Non-Technical Member.

  • Can deploy required Template
  • Gets direct link access.
  • Delete own deployments.
  • limited side bar items

Deployed services and projects remain hidden by default unless granted specific access by owner or admin.

Exception or Error

No response

Version

v4.0.0-beta.285

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant