Roles & Permissions
Every user in Konductro has a role that determines what they can do. Roles are assigned per project — the same person can be a Developer on one project and an Architect on another.
Role Summary
| Role | Responsibilities |
|---|---|
| SDM | Plans phases, generates stories, manages sprints, assigns work, oversees delivery |
| Architect | Produces architecture documents, reviews technical decisions |
| Developer | Decomposes stories into tasks, builds features, creates PRs via UI or CLI |
| Tester | Runs QA test rounds against acceptance criteria checklists |
| UX Designer | Produces design systems and prototypes within Konductro |
Capabilities by Role
| Capability | SDM | Architect | Developer | Tester | UX Designer |
|---|---|---|---|---|---|
| Create and manage phases | Yes | — | — | — | — |
| Planning conversations with Conductor | Yes | Architecture stage | — | — | — |
| Approve artefacts | Yes | Yes | — | — | — |
| Generate and review stories | Yes | — | — | — | — |
| Assign decomposition tasks | Yes | — | — | — | — |
Run /decompose in CLI | — | — | Yes | — | — |
Run /technical-analysis in CLI | — | Yes | Yes | — | — |
| Create and manage sprints | Yes | — | — | — | — |
| Start work on tasks | — | — | Yes | — | — |
| Create pull requests | — | — | Yes | — | — |
| Review pull requests | — | Yes | Yes | — | — |
| Run QA test rounds | — | — | — | Yes | — |
| Manage design systems | — | — | — | — | Yes |
| Build prototypes | — | — | — | — | Yes |
| View sprint boards and dashboards | Yes | Yes | Yes | Yes | Yes |
Role Assignment
Roles are assigned when a user is added to a project team. The project SDM manages team membership and role assignments from Project Settings.
Authentication is handled by AWS Cognito — Konductro does not store passwords. Users sign in once and have access to all projects they belong to.