Omniscio

Plugin access to Team Chat

A plugin you approve can read the Team Chat channels and direct messages you pick, and search inside them. A plugin with permission to post can also post, reply in a thread, react and send a direct message there, and it asks you first every time. It reads as you, so it never sees a conversation you are not in. It is off until you turn on Plugin access to Team Chat in Settings, Labs, and it works only while Team Chat is on and you are signed in.

On this page

What it is

A plugin can ask for two permissions, shown on its install card:

Permission What it lets the plugin do
Team Chat (teamChat.read) Read the Team Chat channels and direct messages you pick, and search inside them.
Post in Team Chat (teamChat.write) Post, reply, react and send direct messages in the channels you pick, after you approve each one.

Both are elevated permissions. A plugin that asks for Post in Team Chat must also ask for Team Chat; one that lists it alone cannot be installed or published.

Where to find it

  • The switch: Settings, Labs, Plugin access to Team Chat. It starts off and hidden. While it is off, while Team Chat is off, or while you are signed out, every read and the picker are refused.
  • The picker: a plugin's panel opens it. You tick single channels and direct messages, or All, including new ones, which also covers conversations you join later. Below the list you choose how the plugin's posts will appear: Under your name, labeled "sent by" the plugin (the default) or As its own card named after the plugin. The picker shows your current choice the next time it opens.
  • Review and take back: Settings, Plugins, the plugin's access panel lists each picked conversation (a direct message is marked as one) and All your channels and direct messages, each with Revoke. Every read is written to the plugin's read log.

What a plugin can and cannot do

  • Can: list the picked conversations you are still in, with their names and whether each is a channel or a direct message; read their messages newest first, a page at a time; read a thread's replies; see how many messages you have not read in one and when you last read it; and search inside the picked ones.
  • Cannot: read a conversation you did not pick (it is told "That channel is not available." before Team Chat is asked anything), see a conversation you are not in, see search hits from conversations you did not pick, or see mentions, reactions, attachments or the internals of alert, call and bot messages. Each message carries only its id, its author's id and name, its text, its time, the message it replies to, whether an agent posted it and, for a plugin's post, the plugin's label.
  • Can, with Post in Team Chat: post a message in a picked channel, reply in a thread there, add or remove a reaction on a message there, and send a direct message in a picked direct message conversation (or to anyone, if you chose All, including new ones). Each one asks you first.
  • Cannot, even with Post in Team Chat: post anywhere you did not pick, send a direct message to you yourself, edit, delete or pin a message, mention people, attach files, or turn off its own asks. A plugin that posts as its own card cannot reply in a thread.

How it behaves

  • Picks belong to the Team Chat workspace that was active when you picked them. If you switch to a different workspace, those picks do not apply there until you switch back.
  • Leaving a channel ends the plugin's view of it, because every read runs as you.
  • Search looks at up to 50 matches, drops every one outside your picked conversations, then returns at most 20 (the plugin can ask for fewer).
  • A plugin can make at most 60 reads a minute, shared with its other work-data reads.
  • Turning the switch off stops the very next read, with no restart.

Asking you first

Before every post, thread reply, reaction and direct message, the app shows its own dialog with the plugin's name, the channel (or the person a direct message goes to), whether it will show under your name, labeled "sent by" the plugin or as the plugin's own card, and the whole text. Only your Allow sends it; Cancel, closing the dialog, or no window to show it means nothing is sent. A reaction always shows under your name, and the dialog says so. If you take the plugin's access back, or change how its posts appear, while the dialog is open, nothing is sent.

Four switches in Settings, Plugins turn these asks off one at a time: Ask before a plugin posts in Team Chat, Ask before a plugin replies in a Team Chat thread, Ask before a plugin reacts to a Team Chat message and Ask before a plugin sends a Team Chat direct message. They are on by default and only you can turn them off: an agent that tries gets a card you must answer. They show while Plugin access to Team Chat is on.

Every change, and every refusal after the plugin named a picked conversation, is written to the plugin's change log in its access panel ("Posted in Team Chat", "Added a reaction in Team Chat", "Removed a reaction in Team Chat", "Sent a Team Chat direct message").

Limits

  • A message page holds 1 to 100 messages (25 by default).
  • The picker lists up to 200 conversations.
  • A thread read returns up to 500 replies and says when there were more.
  • A post or direct message is 1 to 8,000 characters; a reaction is 1 to 32 characters.
  • A plugin can make at most 10 changes a minute, shared with its other work-data changes.

Speed cost

Not measured yet. The feature adds no background work of its own (no timer, poller or watcher); it only does work when a plugin calls it, and each call is capped at 60 reads a minute. A channel list reuses Team Chat's own 30 second channel cache, and a message read reuses its live answer cache. The off-and-on measurement in the shared Speed Cost Format needs a plugin that actually uses this permission, and is owed before the feature goes to dogfood.

Plugin access to boards and tasks, Plugin access to your calendars and Plugin access to people's schedules explain the sibling work-data permissions, Team Chat explains the chat itself, the Plugin Marketplace page covers installing plugins and the consent card, and Plugin Developer Mode explains how a self-built plugin can use these permissions before the marketplace lists them.

Last verified 2026-11-12