Decide two things about the working group you are creating:


| Field | What to enter |
|---|---|
| Name | Required, at least 3 characters. Name the working group, not the project: Platform Team, Marketing Ops. |
| Parent Folder | Leave empty for a root folder, or pick a parent to nest under. Clear removes a selection. |
| Can contain boards | On if the folder will hold perpetual boards. |
| Can contain cycles | On if the folder will hold cycle boards. Turning it on reveals the three fields below. |
| Cadence for Cycles | Required with cycles. DevStride creates one cycle board in this folder for every timebox of the cadence, past and future. Only active cadences are offered; Manage Cadences jumps to settings. |
| Status Collection for Cycles | Required with cycles. The statuses (columns) every cycle board in this folder uses. |
| Default Team for Cycles | Optional. Pre-fills the Team field when you create an item while viewing one of the folder's cycles. |


A root folder has no parent to inherit from, so you choose its starting access:
| Option | Who gets access |
|---|---|
| Public — anyone in your organization (default) | Everyone can view and edit immediately. |
| Team — team name | Only members of the selected team can view and edit. Offered when Can contain cycles is on; picking a Default Team for Cycles switches to this option automatically. |
| Private — only to you | Starts visible only to you. Invite users or teams, or set organization access, later from Permissions. |
A nested folder shows no Visibility choice. Instead the dialog notes Folders inherit permissions from the parent folder. You remain the folder's Owner either way.
Open the folder and click Edit (or right-click it and choose Edit). Everything stays editable except:
Import Stories and Epics into Boards
Put existing work items onto a board with the Import button — browse or search the workstream map, filter, select, and import — plus the other ways to assign an item to a board.
Manage and Edit Dependencies
Record what blocks what from a board card, read the Relationships dialog, and see dependency lines — including other teams' work — on the 2D board view.