## Problem to solve In most cases no developer works alone on the Clonio instance. Maybe there are some different roles too. ## Proposed solution Team can have users. So users get invited to a team. On registration, each user creates his own team. Within a team there are roles: developer, devops, auditor, manager - developer can CRUD clonings - devops can manage database connections - manager can invite users - auditor has access to all auditlogs ## Alternatives considered - ## Who benefits? Users in dev teams ## Acceptance criteria <!-- How do we know this feature is done? List concrete, testable conditions. --> - [ ] - [ ] - [ ] ## Additional context -
Problem to solve
In most cases no developer works alone on the Clonio instance. Maybe there are some different roles too.
Proposed solution
Team can have users. So users get invited to a team. On registration, each user creates his own team.
Within a team there are roles: developer, devops, auditor, manager
Alternatives considered
Who benefits?
Users in dev teams
Acceptance criteria
Additional context