Skip to main content

Team chat

Team chat lets teammates collaborate in a single shared Glean conversation, where each person can prompt Glean and build on the same thread. It's off by default. Turn it on and choose who can use it. For how people use it, see Team chat.

Turn on team chat​

  1. Go to Admin console → Assistant → Team chat.
  2. Choose who can use it:
    • On for everyone — every user in your workspace can start and join team chats.
    • On for some teammates — only the individuals or groups you select can use it.
    • Off — no one can start or join team chats.
  3. Click Save.

Changes take up to 30 minutes to take effect.

tip

Enable team chat for a whole working team rather than a handful of individuals. The feature only works between people who have it turned on, so a group that's too small feels limiting. People without it enabled can only view a shared chat, even when other participants have it on.

How permissions work​

Sharing a chat doesn't change anyone's access to underlying data. Each message runs with the permissions of the person who sent it, so Glean draws on what that person can access and labels each message with its author. Teammates can read answers already generated in the thread, but they can't open source documents they don't have permission to see. Sharing a chat shares the conversation and its output, not anyone's credentials.

Glean doesn't restrict responses to the lowest access level shared by all participants. This allows more flexibility in bringing in colleagues with context that others don't have.

Considerations before a broad rollout​

The current model assumes people exercise judgment about what they ask in a shared room, the same way they would in a meeting or a group channel. For most teams this maps well to how they already work.

Responses post to the thread as Glean generates them, so there's no review step before other participants see them today. Human-in-the-loop review controls are on the roadmap.

Artifacts don't have their own permissions yet. Giving someone edit access to a chat lets them edit every artifact in that conversation, which is what makes co-authoring work. Let your users know that adding someone to a chat also grants edit rights on everything the thread has produced.

See also​

  • Team chat — how people share chats, collaborate on artifacts, and work with Glean in a shared thread
  • Chat Sharing — admin controls for sharing read-only conversations