Proposed Permission Structure for Team Roles

[eliasnau]

Revised Permission Structure

Currently, all team members have the same level of deletion authority, regardless of their role (owner, admin, or regular member). This means any team member can delete any deployed service or project, even if they didn't create it.

Proposed Permission Structure:

• Owner:

  • Full access to manage all services and projects.
  • Can create, edit, delete, deploy, and view all projects.
  • Deployed services and projects are hidden by default and can only be made visible by the owner.

• Admin:

  • Can manage and delete services and projects created by members, but not those created by the owner.
  • Can create, edit, delete, and deploy services and projects within their scope.

• Member:

  • Can only delete their own deployed services and projects.
  • Can view and collaborate on assigned projects, but cannot modify or delete anything outside their own work.

• User (Bonus Role - Non-Technical Member):

  • Can deploy required templates and manage their own deployments.
  • Can delete their own deployments.
  • Limited sidebar options to reduce complexity.
  • Deployed services and projects remain hidden by default unless explicitly shared by the owner or admin.

This structure ensures that permissions are more aligned with the roles and responsibilities of each team member, improving control over who can delete or modify important projects and services.