TEAM OPS · 3 MIN READ

Team chat + groups

Three channel types in one panel: the org-wide Company channel, 1:1 DMs, and admin-creatable named Groups.

Company channel

Everyone in the org sees it. Use for announcements, wins, broad questions. Pinned at the top of the chat sidebar.

Direct messages

Private 1:1 conversations. Admins do NOT have read access to DMs through any API — privacy matters for adoption. (Audit log records that a DM happened, not its contents.)

Groups

Named multi-person chats. Use for project teams, regional pods, or temporary working groups.

Create a group

Open Team Chat. In the sidebar's Groups section, click the + button.
Name the group (e.g. "SLC reps", "Q3 launch", "Marketing").
Add members one by one OR click a team chip to add a whole team at once.
Click Create group. You're auto-added as the creator.

Group settings

Click the cog in the group header → rename, add members, remove members (creator + admins only), leave the group, or delete the group (creator + admins only). Empty groups auto-delete.

Notifications

First time you open Team Chat, OraTek asks for browser notification permission. Approving means:

Org-channel messages → in-app banner + OS notification
DMs → in-app toast + OS notification
Group messages → unread badge + OS notification

Notifications fire only when the tab isn't visible AND you're not viewing that exact channel — no double-pinging.

Julie + team chat

"Post in the company channel: just closed Banner Health" → confirmation → sent. She can post to org, DM a specific teammate, or post to a group by name (call list_chat_groups first if she doesn't know the group_id).

No named channels beyond groups. If you ask Julie to "post in #general", she'll tell you there's no such channel and ask which one you meant — she won't silently route to the Company channel.