You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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:
Admin:
Member:
Bonus: Consider a "User" role for a Non-Technical Member.
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
The text was updated successfully, but these errors were encountered: