Quick start: under a minute
The whole setup is designed to fit inside one coffee order.
- Create a workspace: name it, pick the tracks your cohort runs (Web Dev, AI, Cloud, UI/UX…), add a description. The creator is enrolled as an approved LEAD with full navigation instantly.
- Invite your cohort: use the invite flow or share the workspace link. Incoming requests land in an approval queue. Accept in one tap.
- Create a project & first sprint: projects group work (e.g. “Final Capstone”), sprints set the timeframe, and tickets carry the actual tasks.
- Drag a ticket to DONE: that's the whole loop. Open sprints never auto-close, so late work doesn't vanish.
Pro tip
Roles that hold the line
One workspace, four roles. Each sees exactly what their job requires.
| Role | Sees & does | Boundaries |
|---|---|---|
| ADMIN | Full workspace control, invites, approvals, and permissions. | Oversight role for the program office. |
| LEAD | Everything: sprints, documents (edit), members, agile history, exports. | Can create and delete workspace-level structures. |
| SUB_LEAD | Task board and analytics; assists with execution and review. | Documents and members stay read-mostly. |
| STUDENT | Their private ticket instances, assigned work, and granted documents. | Group tickets appear as private instances, with no cross-student visibility. |
Enforced where it counts
Task board: projects → sprints → tickets
Three levels of organization, one drag-and-drop surface.
Projects are the top container. Inside each project you create sprints, and inside each sprint live the tickets. Tickets flow across PENDING → PROGRESS → DONE.
- Bulk-assign by track: assign an entire track's students to a ticket in one action, and assignment emails fire automatically.
- Private instances: a group ticket gives each assigned student their own instance to move and comment on privately.
- Filter & search: filter by track or completion state, and search tickets across the board.
- Attach & link: add file attachments and link tickets to documents in the Document Hub so specs live one click away.
- Comments: keep review loops on the ticket, not in chat.
Document hub: a living knowledge base
Authoritative specs, subpages, and attachments, organized like a tree, not a folder dump.
- Create root documents & subpages: build hierarchy naturally (e.g. “Project Brief” with “System Design” and “Edge Cases” underneath).
- Markdown editing: a full editor with autosave (about 2 seconds after your last edit), Ctrl/Cmd+S for instant sync, and a cloud-sync indicator.
- Attachments & icons: files live with their document; icons give the tree a quick visual scan.
- Tag colors: automatically applied so status is legible at a glance.
- Lead-only documents: flagged documents hide from students unless a lead grants explicit access.
Permissions & access
Explicit beats implicit. Grant access to exactly the right people.
- Workspace membership: approved members only. Requests and invites both flow through the approval queue.
- Document access: leads grant view or edit on specific documents; grants can inherit down the subpage tree.
- Server-side filtering: students never even receive lead-only content in API responses; it isn't hidden in the UI, it's absent from the payload.
Agile history: proof, not anecdotes
Velocity, predictability, and scope churn without the spreadsheet chore.
- Metrics: velocity trends, predictability scores, scope churn, and burndown, aggregated per project across every sprint.
- Export: one click to XLSX for reporting to program leadership.
- Course-correction: spot the sprint where scope crept and adjust the next one, and that's the whole point of measuring.
For students: your daily loop
You don't need the whole manual. Here's your day.
- Open the workspace you're assigned to from the workspace switcher.
- Head to the Task Board, find your sprint, and open the ticket you're working on; it's your private instance.
- Read the linked document in the Document Hub for the full spec; the countdown on the sprint tells you how much runway is left.
- Move your instance through PROGRESS → DONE, commenting and attaching files as you go.
Can't see a document?
FAQ
Can multiple sprints be open at once?
Yes, by design. Open sprints never auto-close, so a student can keep working across several open sprints at the same time. You close a sprint when the work is actually done.
How do I change someone's role?
Open the Members view in the workspace, find the member, and update their role. Changes apply immediately, and permissions are re-resolved server-side on the next request.
What happens when I delete a ticket or document?
Only leads and sub-leads can delete. Deleted items are soft-deleted and recoverable for a grace period; the board automatically moves you to the nearest remaining document.
My email link expired. What now?
Verification links last 24 hours and reset links last 1 hour. Re-request a new one from the login or verification screens; the resend path is instant.