The rest of this guide uses a few DevStride words constantly. Get these six straight and the configuration steps will make sense.
| Term | Meaning in one line |
|---|---|
| Workstream | A container in Map Value for what you deliver (a product, initiative, or function). Nestable; top-level ones are core workstreams. |
| Item | A unit of work that lives in a workstream and carries a type, status, assignee, dates, and estimates. Opens in its workspace (the item drawer). |
| Item type | The level an item occupies in your hierarchy (Epic → Story → Task). Types decide what can nest under what and which fields appear. |
| Board | Where a team executes in Plan Delivery: columns are statuses, cards are items. Perpetual boards run forever; cycle boards are tied to a cadence. |
| Cadence | A repeating interval you define in Settings (two-week sprint, month, quarter). It generates the dated timeboxes that cycle boards run on. |
| Cycle | One timebox of a cadence as seen on a cycle board — "Sprint 12", with its own start and end dates. |
Everything else, from assignee to WIP limiter, is defined in the full glossary.
Next: Setting Up Users and Teams.
Admin Onboarding - Getting Started
Step 1 of admin onboarding — confirm your organization exists, complete your Organization Profile (name, domain, logo, timezone), choose the Global Automations defaults, and learn your way around Configure Settings.
Admin Onboarding - Setting up Users and Teams
Step 3 of admin onboarding — invite your people, give fellow administrators the Admin role, and create a team for every working group so later steps have someone to assign work to.