You have now configured both halves of DevStride's model. This page is the recap you can hand to the next administrator.
| What you set up | Where | What it gives you |
|---|---|---|
| Organization, users, teams, roles | Configure Settings → Organization; roles under Admin → Permissions | People to assign to, and access boundaries |
| Workstreams and item types | Map Value; Settings → Item Types | The what: a value hierarchy that reports roll up by |
| Custom fields, tags, forms, priorities, estimates | Settings → Data Model | The data each item carries |
| Status collections | Settings → Data Model → Item Statuses | Board columns and the vocabulary of "where is it?" |
| Folders, boards, cadences | Plan Delivery; Settings → Cadences | The who and when: team queues, perpetual or in cycles |
| Gantt charts | Track Progress | The timeline view with dependencies |
| Reports | Measure Performance | Progress, throughput, velocity, cycle time, churn |




API Keys
Orientation for new admins: API keys give scripts, integrations, and the DevStride MCP server programmatic access with the creating member's permissions; each member manages their own under My Account.
Handling incomplete items from Sprint to Sprint
A low-touch way to carry unfinished work into the next sprint without losing the record of what each sprint actually delivered: split the story, close part 1, estimate part 2.