Slack is a cloud-hosted communication platform that combines channels, direct messaging, and app integrations for teams. It supports collaboration, information distribution, and workflow automation through many integrations. Slack is primarily used for daily coordination, team communication, and reducing email noise.
Use this profile to understand the building block briefly, place it in the model, and open related building blocks.
Usable application software: supports people in a task.
Concrete cog in the system that works inside larger relationships.
Slack is a cloud platform for team messages, channels, direct messages, and integrations.
Slack was released in 2013 by Stewart Butterfield and the Slack team as an evolution of Tiny Speck's internal communication system.
Workspaces contain public or private channels and direct messages. Messages, threads, files, and apps connect communication with workflows; search and notifications shape everyday findability.
A channel groups communication by team, topic, or workflow.
Threads keep replies with the originating message and reduce noise.
Apps and APIs trigger actions or provide system information in Slack.
Slack fits fast coordination and integration-rich teamwork. Retention, access, guests, notification rules, and the boundary around authoritative documentation require governance.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.