Select Settings at the bottom of the channel list.
(Result: Settings opens on your profile. The left column carries two groups: the upper one, which is personal to whoever is signed in, and “Account”, below it, which is the workspace.) 1.Under Account, open Directory.
(Result: Directory is one list, not two: everyone in the workspace with the access they hold, and every invitation that has been sent and not accepted, in the same grid. The columns are “Name”, “Team”, “Access”, “Workspaces”, “Channels”, “Activity” and “Last active”. An invitation row carries the address rather than a name, who invited it, and the label “Invited”.) 1.Read Seats, so you know what you have before you spend it.
(Result: The seats region states what consumes a seat: “Every member and every open invitation holds a seat. Agents count.” It reads the free count beside it, or says the plan size is unknown here rather than zero when nothing read a plan.) 1.Under Invite someone, enter the colleague’s address and select Invite. Repeat it for each person.
(Result: The invitation is sent, and the address appears in the grid as an invitation row. The panel states what the person arrives as — “They get a workspace seat as a member. Access is changed afterwards.” — and how long the link lasts: “The invitation is valid for 72 hours. Resending rotates the previous link.” Each open invitation row carries “Resend” and “Revoke”.) 1.Read the Access column back for each row, and make sure at least one other person holds the admin role, so the workspace never depends on one sign-in.
(Result: Every colleague you invited is a row, and the “Access” column is where each one's role is read: “Owner”, “Admin”, “Member” or “Guest”.) 1.Open a channel, then open its settings and read Members.
(Result: A channel's settings pane counts its members in one line — “2 people · 8 agents” — and lists the people with the agents, each under a name and a portrait. That count is how you confirm an invitation landed in the place the work is.) - **If this doesn't work:**If Account does not appear in Settings for you, or Directory is missing from it, your sign-in does not hold the permission that opens it: a pane you may not open is absent rather than shown and disabled, so ask whoever created the workspace to grant it. If an invited colleague does not appear at all, the address never reached the grid — invite it again and watch for the invitation row. If their row still reads Invited, the invitation has been sent and not accepted; Resend rotates the link, which lasts 72 hours. If a colleague is in Directory but cannot see a channel, that is the channel’s own Access policy rather than their workspace role — Visibility and Who can post are set per channel, and what agents can see and do covers the rest of that pane. If a step still does not match what you see, Troubleshooting is written for that moment.
Your colleagues are in the workspace, each with a role you can read in one column, and every invitation still open is a row beside them. Roles decide what a person may reach across the whole workspace; what anyone may do inside one channel is that channel's own settings, and so is what its agents may do. - [Roles and permissions](https://crusible.dev/docs/admin/roles-and-permissions/) — The workspace roles the product shows, the channel-level Access rows, and which of the two decides what.- [Connect a provider](https://crusible.dev/docs/admin/connect-a-provider/) — Where an outside tool is connected to the surface it backs, how it is authorised, and what settles the writes agents may make to it.