Guide
How to work with clients and vendors in your AI workspace, safely
At some point a client asks to see progress in real time, or a contractor needs to be looped into a project thread. The instinct is to just add them to a channel. That's usually a mistake, because a normal team channel carries far more than the one thread they need. Here's a setup built for exactly this instead.
Why not just add a client to a regular channel?
A normal team channel accumulates context over time: pricing debates, other clients mentioned by name, internal disagreements about a vendor. Adding an outside person to that channel, even for one good reason, means they can now scroll back through all of it. Removing them later doesn't undo what they already read.
Email avoids that problem but throws away the benefit of shared, AI-assisted chat entirely. What's needed is a room built for outside people from the start, not a regular channel with an exception carved into it.
What a guest channel actually is
A guest channel is a restricted room. A guest added to it sees that room and nothing else in the workspace, no other channels, no DMs to individual teammates. It's the digital equivalent of a conference room booked for one meeting, not a badge to the whole building.
Guests get a chip on their name, visible to everyone in the room, so the team always knows who's inside the company and who's a guest reading along. There's no ambiguity to manage by memory.
The AI lockdown matters more than the room boundary
A room boundary alone would still carry risk if the AI answering questions inside it pulled from the same company-wide context it uses everywhere else. A well-phrased question from a guest could then surface something the room was never meant to expose, even without anyone reading old messages.
In a guest channel, Glitch answers without company data at all, no snapshot, no shared memory, no tools. That's a second, independent lock on top of the room boundary. Even a guest who asks exactly the right question gets nothing beyond what's written in that room.
Three practical room setups
A client room works well for sharing progress and deliverables on a project, a status thread the client can check without pinging anyone directly. It gives them visibility without giving them the company.
A vendor room keeps the people supplying you in their own space, separate from anything client-facing, useful for coordinating orders or timelines without exposing internal pricing conversations. A contractor room does the same for someone doing a defined slice of work, scoped to just that project's history for as long as they're engaged.
What guests can't do
Guests can't DM anyone on the team. Whatever needs discussing happens in the room, visible to whoever else is in it, not in a private side channel that's invisible to the rest of the company.
None of this costs extra to set up. There's no per-seat pricing, so adding a client room or a contractor room doesn't change the bill.
Common questions
Can a guest see other channels in our workspace?
No. A guest only sees the room they were added to. Nothing else in the workspace is visible to them, and they can't browse or search into other channels.
Does the AI use our company data when it answers a guest?
No. Inside a guest channel, Glitch answers without company data, no snapshot, no shared memory, and no tools. It only has access to what's written in that room.
Do guest rooms cost extra per person?
No. Pricing is flat by tier, not per seat, so adding a client, vendor, or contractor room doesn't add a line to the bill.
See it working, not described
The sandbox is a seeded company you can wander. No signup needed.