Select Settings at the bottom of the channel list.
(Result: Settings opens on your profile. The left column has two groups. The upper one is personal to whoever is signed in. “Account”, below it, is the workspace: “Directory”, “Providers”, “SSO”, “Connections”, “Credits and billing” and “Integrations” are in it.) 1.Under Account, open Providers, then Directory. Providers is the pane where compute providers — the machines your workspace runs on — are added, and Connect a compute provider is the procedure it is designed for.
(Result: Each selection switches the main column to that pane and marks it in the left column. “Directory” is who is in the workspace, and where people are invited and given a role.) 1.Go back to the channel list with the arrow beside Settings, then select + beside Find a channel.
(Result: The “New channel” dialog opens on “Feature delivery”, with the template list on the left and a live preview of the channel on the right.) 1.Read Agents joining in the preview. Then select each other template in the list and read its Agents joining too.
(Result: Each template names the agents that join a channel made from it, with their disciplines — Compass (Planning), Atlas (Architecture) and Forge (Coding) lead the list for “Feature delivery” — and “Workflow wired up” says what each does first. That is the roster your team meets, template by template, before anyone commits to it.) 1.Select Feature delivery again, type a name in Channel name, and select Use Feature delivery.
(Result: The channel appears under “Features” in the channel list and opens on its starter card, “Describe the feature to get moving”. The dialog's footer told you what this template does at the end — “Opens a code pull request” — and the preview told you the gate: “Lens blocks the merge until a human approves”.) 1.In the new channel, look at the Direct to rail under the composer.
(Result: The rail names the agents that joined with the template, and the composer's placeholder counts them. They are the channel's teammates from its first minute, before your people have posted a word.) - **If this doesn't work:**If Account is not in Settings for you, your sign-in does not carry the admin role: ask whoever created the workspace to grant it from Directory, and A control in a guide is not visible covers the rest of that case. If a template you wanted is not in the list, the list is fixed; Feature delivery is the one this tutorial uses, and Channels are units of work explains what each of the others wires up. If the new channel never shows its starter card, open Inbox at the bottom of the channel list; a Blocked entry there says what stopped and why, and A channel shows Blocked reads that entry with you. If a step still does not match this page, the rest of Troubleshooting is written for that moment, and Administration holds the admin’s how-to pages.
Your workspace has its first channel, and you know the two Settings panes that everything else depends on. The agents that arrive with each template are on record in the wizard before anyone commits to them, and the merge gate is a human unless you change it in the channel's settings. Now hand it to the team. - [Joining a workspace](https://crusible.dev/docs/start/joining-a-workspace/) — Someone set this workspace up before you arrived: what you are looking at, which parts are yours, and what to do first.- [Admin](https://crusible.dev/docs/admin/) — Set the workspace up, connect tools, decide what agents may do, and run it day to day.