Guest access that gives a client one channel, not your whole company

Guests are invited from the same Invite people dialog that adds teammates, on its External guest tab. The tab is available to organisation admins — the permission to manage huddls — rather than to every member, so nobody outside the company gets in because a channel owner was being helpful.

• One guest can be invited to more than one huddl, each with its own channels, and a huddl can hold any number of guests.
• A guest’s profile shows their name, title and local time. Email and phone are hidden from other guests, and a guest viewing a member’s profile sees no contact details either.
• The admin pages list every guest in a huddl on their own tab, apart from members, with the invite button beside them.

The admin enters the guest’s email address and ticks the channels the guest may see, from the huddl’s list of active channels. The guest receives an email, accepts, and lands in that huddl with those channels in the sidebar. Everything about the guest from then on carries a Guest mark beside their name: in messages, in channel member lists, in search results and on their profile, so nobody mistakes a client for a colleague when deciding what to say.

Inside their channels a guest is a full participant: they read and post, reply in threads, react, pin, save messages, drag files in and search — but search covers only the conversations they belong to, as it does for everyone. The rest of Huddl is simply absent for them: the create-channel control is not shown, nor is the invite control, nor the organisation’s other huddls, so there is nothing for a guest to ask for and be refused.

A guest cannot send a broadcast. The composer offers @channel and @here only to members, so a client cannot page the whole channel at midnight. Direct messages work the other way round: a member chooses, in their own privacy settings, whether guests may start a direct message with them. A guest you already share a conversation with can always reply.

Nothing in the rest of Orbiz opens for a guest account. Cadence boards, Filespace folders, people records and payroll stay behind the organisation’s own logins; the only way a file reaches a guest is when a member shares it in a channel the guest is in.

The simplest pattern is one private channel per client account, with the client’s lead as its guest. The account team talks to the client there, keeps its own internal channel for the things a client should not read, and the two never mix because the guest cannot see the second one exists.

An organisation can also create several huddls — one for the company and one per client or project — each with its own channels and members. A guest invited to a client’s huddl sees that huddl alone. Agencies with many accounts tend to prefer this: the client’s huddl can carry a general channel, a channel per campaign and a channel for files, and the guest’s sidebar reads like a workspace built for them.

On the Guests tab an admin chooses Revoke access. The guest’s account is deactivated and they can no longer sign in to Orbiz; their messages stay in the channel history, attributed to them, so the record of what was agreed is intact. Removing a guest costs nothing and frees nothing, because a guest never took a seat.

A member who leaves the organisation is handled by the organisation’s own offboarding, not by Huddl, and a message from a former member reads as such wherever it appears.

Nothing per guest. Huddl is one of the ten tools in the Orbiz flat price per organisation, set by the organisation’s own headcount band, and guests are not counted in that headcount. Slack prices its single-channel guests at nothing and its multi-channel guests as a paid seat, on paid plans; Pumble includes five single-channel guests per paid seat and charges for multi-channel guests. In Huddl a guest in five channels and a guest in one cost the same: nothing.