Slack

What Slack is and how it organises work

Slack is a cloud collaboration platform developed by Slack Technologies, part of Salesforce since 2021. It organises much of workplace communication around topic-based channels, with direct messages, search, files, quick meetings and integrations. It is proprietary software offered through free and subscription plans, rather than an open protocol that an organisation can freely install on its own server.

The underlying idea is shared context: someone joining a project can consult accessible conversations instead of relying entirely on forwarded email. Value does not come from collecting messages. It comes when channels have a purpose, decisions are identifiable and important information remains discoverable after the discussion.

Reference documentation: Building Slack — Day 1, first-person history · Salesforce — Slack acquisition completed · Slack — Plans and features.

From the Glitch game to Salesforce

Slack emerged from Tiny Speck’s work on the online game Glitch. Stewart Butterfield’s team had used IRC and internal tools to coordinate; after closing the game, it turned that experience into a communication product. Its founders include Butterfield, Cal Henderson, Eric Costello and Serguei Mourachov. The August 2013 preview should be distinguished from the general public launch on 12 February 2014.

• 2018: Slack closed its IRC and XMPP gateways in May. Its July agreement with Atlassian involved the transition from HipChat and Stride as those services were withdrawn.
• 2019: Slack became publicly traded through a direct listing, distinct from a conventional offering of newly issued shares.
• 2020: it acquired Rimeto, an employee-directory and profile specialist that preceded Slack Atlas.
• 2021: Huddles arrived in June as an audio-conversation feature. Salesforce completed its Slack acquisition on 21 July, following the agreement announced in December 2020.
• 2024–2026: Lists expanded task management, while AI developed from summaries and search into integrated agents and the redesigned Slackbot.

Leadership changed too: Lidiane Jones and Denise Dresser led Slack after Butterfield. Salesforce’s October 2026 corporate source identifies Rob Seaman as executive vice president and general manager. This chronology does not make historical functions current: IRC gateways, for example, are no longer a supported access route.

Reference documentation: Building Slack — Day 1, first-person history · Building Slack — Year 1 · Nieman Lab — Slack direct listing · Atlassian — Slack partnership · Slack — Rimeto acquisition · Salesforce — Slack acquisition completed · Slack — Product update archive · Salesforce — Current Slack leadership · Bizjournals — Leadership succession · Salesforce — Lists launch.

Conversations organised by topic

Slack organises communication through channels and messages. Threads group replies around a specific message, allowing a topic to develop without mixing every discussion into the channel. For an OSH team, usefulness depends on agreeing what belongs in each space and how a discussion’s conclusion is identified.

A conversation is evolving information, not necessarily an approved reference. It may contain questions, hypotheses and corrected versions. Separate the exchange that helps explain a problem from the document or register retaining the final decision. This reduces the risk of finding an old answer and applying it outside its context.

Reference documentation: Slack Help — Use threads to organize discussions.

Workspaces, channels, threads and search

A workspace provides an organisation or community’s environment. Public channels are discoverable by workspace members; private channels restrict participation. Direct messages serve exchanges between particular people. A public workspace channel is not the same as a publicly indexed web page.

A thread keeps replies attached to a message. Mentions direct attention and reactions provide brief responses, but teams must agree what those signals mean. A seen reaction may acknowledge receipt without indicating technical review. If a discussion changes a procedure, its conclusion should state the decision, who confirmed it and the current reference.

Search supports modifiers such as in: for a channel, from: for a person and before: or after: for dates. Combining them helps reconstruct a specific exchange, subject to access and retention. An empty search may reflect missing permission, deletion or different terminology, rather than proving that an event never occurred.

Slack Connect links organisations while retaining their separate workspaces. A guest instead accesses authorised channels within the host workspace. Temporary collaboration needs an invitation owner, a defined information scope and an access end point. Establish these before sharing material, rather than after discovering external participants in the channel.

Reference documentation: Slack Help — Use threads to organize discussions · Slack — Search · Slack — Connect guide · Slack — Guest roles.

From conversation to documents and tasks

Huddles support audio or video conversation, screen sharing and an associated thread. Free plans allow two participants; paid plans allow up to 50, with at most 25 simultaneous video users. They suit questions that require looking at material together. Audio and video clips provide explanations without requiring everyone to be available at the same time.

A canvas holds more stable content than a message, such as a project brief, instructions or notes. Its value depends on editing, permissions and maintenance. A preventive-work guide should identify its version and owner and link to the approved source. A convenient explanation does not automatically become the process’s official document.

Lists add items with fields, assignees, dates, views and their own threads, with CSV import and export. This separates a task from the messages discussing it: conversation supplies context while the item retains status. A completed field establishes only what the process defines as completion.

For example, a campaign may use a canvas for its purpose and materials, a list for deliverables, and a channel for questions. Each component has a role. Repeating the same date in all three without a primary reference creates discrepancies when the schedule changes.

Reference documentation: Slack — Huddles · Slack — Canvas · Slack — Lists · Salesforce — Lists launch.

Integrations, APIs and automation

Slack connects services through applications and programming interfaces. An integration may display an external file, notify a change or start an operation elsewhere. Distinguish displayed content from its storage location and each application’s permissions. The July 2024 Box partnership, for example, introduced Box AI queries within Slack subject to access to the underlying Box files.

Workflow Builder arranges automation around a starting event and subsequent steps. A simple workflow might collect a request, create an item and notify its owner. Define minimum input, a request identifier and behaviour when an intermediate action fails. Retrying should not create indistinguishable duplicate tasks.

Agentforce brings Salesforce agents into conversations, but it is not a synonym for every Slack bot and does not automatically grant access to all applications. Administrators control installation, identities and actions. A natural-language request affecting data needs a clear path to the system executing the operation.

In OSH work, an automatic notification can route a question to the appropriate owner. The technical answer and closure remain in their corresponding process. Validate a pilot with a normal request, an incomplete one and a repeated one, checking both result and recipient.

Reference documentation: Slack — Workflow Builder · Salesforce — Agentforce in Slack · Box — Box AI in Slack · Slack — API terms.

Slackbot and contextual AI

The Slackbot introduced in January 2026 extends beyond the historical assistant for reminders and simple responses. It can use authorised workspace context to find information, prepare drafts and help perform tasks. Conversation summaries, huddle notes and assisted search are related capabilities, but availability depends on the plan and should not be confused with unlimited agent access.

Current documentation distinguishes Free and Pro trials, 15 weekly messages per member on Business+, and no such weekly or lifetime message limit on Enterprise+. Salesforce Flex Credits can support certain additional usage. This does not remove every limit: separate conditions and task-execution limits apply.

Slack states that it does not train generative models on customer data and distinguishes those models from machine-learning techniques used for recommendations. That statement concerns its own service; an external application may have different data practices requiring separate review.

A reasonable use is drafting a list of outstanding questions about a guide, then opening the cited conversations before consolidating them. The agent may find a polished older answer and a short later correction. Validation checks which remains current, preserves disagreement and prevents a suggestion from becoming an approved instruction.

Reference documentation: Slack — Plans and features · Slack — Context-aware Slackbot · Slack — Slackbot limits and credits · Slack — ML and AI data principles.

Plans, retention, export and platforms

Free, Pro, Business+ and Enterprise+ combine different collaboration, administration and AI capabilities. Free limits installed applications to ten and ordinary message and file access to the latest 90 days; data older than one year is deleted, with specific exceptions such as Salesforce channels. A later upgrade cannot recover data already deleted.

Distinguishing hidden from deleted content matters for a learning community. A thread outside the search window is not a stable reference. Where retention is configurable, saving or pinning a message does not automatically exempt it. Decide which knowledge belongs in a maintained repository.

Exports can contain messages and file links in JSON. Do not assume they include every binary file or reproduce every feature identically on restoration. Access to private channels and direct messages depends on plan, role and applicable conditions. Private describes participant visibility, rather than an absolute guarantee against administrative access.

Slack offers web access and applications for Windows, macOS, supported Linux distributions, iOS and Android. Requirements change periodically. The former standalone Apple Watch application should not be presented as a current independent client: the January 2018 iOS release note moved that experience into the phone application.

Compare plans against two scenarios: how the team works today, and how it will retrieve a decision a year later. Reconstructing lost knowledge may cost more than an additional feature that sees little use.

Reference documentation: Slack Help — Customize data retention in Slack · Slack — Plans and features · Slack — Free plan limitations · Slack — System requirements · Slack — iOS release archive · Slack — Workspace data export.

Documented incidents and usage debates

Slack experienced an intrusion affecting account information and credentials in 2015, introduced two-factor authentication, and reset additional passwords in 2019 after receiving new information. In December 2022 it reported unauthorised access to code repositories using stolen tokens. According to its investigation, that separate incident did not affect customer data or the production environment. The two episodes should not be conflated.

The 4 January 2021 outage illustrates dependence on a shared service: a team can retain its devices yet temporarily lose its usual communication channel. Operational preparation means agreeing an alternative, how an incident will be announced and where decisions made during the interruption will be recorded.

In 2018, EFF questioned Slack’s suitability for some sensitive communities because of centralisation and privacy controls, while recognising positive practices around government requests. Journalism also examined tensions between continuous conversation, workplace relationships and attention. These are debates about use and design, rather than proof of identical effects in every deployment.

API restrictions affecting external AI and search tools prompted debate in 2025. Current terms restrict uses including LLM training and bulk export by applications offered outside an organisation. Technical access to data does not itself authorise unlimited reuse.

Teams can reduce interruptions by agreeing response expectations, reserving broad mentions and separating informational notices from requests needing decisions. Observe whether the rules improve clarity and leave time for work; message counts alone do not measure effective collaboration.

Reference documentation: EFF — The Revolution and Slack · New York Magazine — Workplace chat reception · Slack — 2015 incident follow-up · Slack — December 2022 security update · Slack Engineering — January 2021 outage · Slack — API terms · Computerworld — 2025 API debate.

Growth and how to interpret success

Public information in May 2015 put Slack above 750,000 daily active users. Its listing registration described more than ten million daily users during the quarter ending January 2019 and over 600,000 organisations. These are historical milestones with specific definitions: a registered organisation, paid account and active person are different units.

Adoption helps explain its integration ecosystem, but does not establish that a particular organisation needs Slack. Selection begins with the problem: scattered conversations, repeated questions, external coordination or decisions that are hard to retrieve. Then test whether the proposed channels, search and repository solve that problem with less effort.

An open community seeking knowledge discoverable through search engines may use chat for discussion while publishing maintained references elsewhere. An internal team’s priorities may instead be identity, retention and integration with existing tools. Those needs matter more than repeating the provider’s growth figures.

Reference documentation: Slack Technologies — S-1/A May 2019 · Irish enterprise department — Slack Dublin, 2015.

Uses for sharing knowledge and coordinating work

• Material queries: open one thread per question and keep clarifications together, identifying who reviews a technical answer.
• Activity coordination: share schedule changes and links to current documents rather than duplicating files in successive messages.
• Learning across teams: exchange experiences with enough context to distinguish local observations from conclusions applicable elsewhere.

These are Sabentis proposals. A channel should not become an improvised route for emergencies or sensitive information. Use the organisation’s defined communication procedures and establish which issues need another process.

Worked example: resolving a question without losing the valid answer

Hypothetical example. Several sites ask how to use a new awareness guide. The team wants to resolve questions without producing contradictory instructions.

1. Post the guide reference with version, purpose and content owner. Explain which questions the channel will handle.
2. Open a thread for each specific question, providing necessary context without unrelated personal information.
3. Separate provisional replies from the reviewed answer. If the guide needs changing, route the issue through its update process instead of improvising a new instruction in the thread.
4. Once resolved, write a short conclusion and link to the current document. Identify questions still open and their review owners.
5. Ensure the reference answer is retained outside the exchange if long-term availability is required. Review workspace permissions and retention policy.

Acceptance means another person can find the valid answer and its context without guessing which message takes precedence. If the guide changes, the old thread should lead to the new reference. Keep the distinction between historical discussion and current instructions visible.

Verifiable case result: 20 questions arrive about the guide. Fourteen have reviewed answers, four require document changes and two await information: 14 plus four plus two accounts for all 20. The channel’s 38 messages are not 38 questions; several clarify an existing thread. The team retains a question identifier, affected version, owner and closure link. A week later, someone uninvolved in the discussion should locate the current answer for three selected questions and distinguish the six still open. This checks knowledge retrieval rather than merely chat activity.

Reference documentation: Slack Help — Use threads to organize discussions · Slack Help — Customize data retention in Slack.

Retention, noise and informal communication

Slack allows retention settings for messages and other content. Its documentation warns that retention also affects pinned or saved items. Pinning a message therefore does not guarantee indefinite preservation. Check the actual policy before using a channel as an evidence archive.

Message volume can hide important information and create expectations of immediate replies. Define what needs a response, who responds and where commitments are recorded. Review members, guests and integrations before posting internal information. If an automatic summary is used, compare it with the conversation rather than treating it as approved minutes without review. A missing message may reflect retention or deletion rather than proof that no discussion occurred.

Reference documentation: Slack Help — Customize data retention in Slack.

When to choose Slack

Slack may fit day-to-day coordination based on topic conversations where the team maintains clear channel and thread practices. If work relies mainly on Microsoft 365 files and groups, compare Microsoft Teams.

Notion can complement conversation by retaining a stable explanation. Selection should consider permissions, retention, search and participant access as well as chat convenience. Agree a route for preserving decisions before the channel becomes busy.

Frequently asked questions about Slack in OSH

Is a pinned message retained forever?

Do not assume so. Retention policies can also affect pinned or saved content.

Does reacting to a message approve an action?

Not unless an explicit process defines that meaning and its evidence. An informal reaction may mean acknowledgement, partial agreement or thanks.

What should move outside the chat?

Current instructions, decisions needing version control and evidence that must be retained under the organisation’s process.

Reference documentation: Slack Help — Customize data retention in Slack.