A channel is more than a conversation: the tab strip along its top is a small, shared desktop. Pin the right artefacts and the team stops asking "where is the current plan?"; pin the wrong ones and the strip becomes a museum of abandoned initiatives. This chapter covers the three extension mechanisms — tabs, connectors, and simple automations — and the discipline of using them sparingly.
Tabs: Persistent Artefacts in the Room
A tab pins one artefact to the channel: a document, a spreadsheet, a planner board, a whiteboard, a website, or a file folder. Good tab candidates share two traits — they change weekly, and the whole channel needs them. The project plan qualifies; the once-a-year policy PDF does not (that belongs in the library, findable by search).
- Cap yourself at five tabs per channel. Beyond that, nobody clicks past the third.
- Name tabs for the question they answer ("Plan", "Budget", "Risks"), not for the tool's product name.
- Review tabs at quarter end and remove the ones nobody opened; the strip is prime real estate.
Connectors: Feeds Into the Conversation
Connectors push external events into the channel as messages: build results, monitoring alerts, form submissions, ticket updates. They are excellent when the channel's job is reacting to those events — an operations channel fed by its alerting system is a control room. They are noise when the feed is merely interesting. One alert source per channel is a workable rule; three overlapping feeds guarantee that real alerts get scrolled past.
Automate the boring middle
Lightweight automation rules can post a welcome message when someone joins, remind owners about expiring documents, or move recurring reports into a thread. Automate rituals, not judgement: anything requiring a human decision belongs to humans. Start with one automation per channel and watch for a month whether it earns its place.
Apps and Bots: Borrowed Capability
The app catalogue adds capabilities — polls, approvals, ticket creation — inside the conversation itself. Two cautions before installing anything: first, each app runs with permissions your administrators granted, so personal installs in shared channels affect everyone; second, every bot message is a message, and channels drown in messages. Prefer apps that people invoke deliberately over apps that announce themselves constantly.
The Dashboard Graveyard, and How to Avoid It
- Before pinning, ask: who opens this weekly? If the answer is one person, it belongs in their personal space.
- Prefer one living document over three snapshots; snapshots rot silently.
- Give every connector and automation an owner named in the channel description.
- Schedule a semi-annual channel tidy: prune tabs, silence stale connectors, archive finished boards.
Used with restraint, extensions make a channel the single place a team works rather than the single place a team talks. That concludes the everyday half of this handbook. The next chapter changes seats: from user to administrator, beginning with a guided tour of the admin console.
