Slack Connect Spaces

Overview

Slack Connect Spaces allow you to leverage the full power of Slack for cross-company teams. A Slack Connect Space represents a shared space in Slack with your external partners and customers, allowing you to create unlimited public and private channels, collaborate using our full suite of tools, and securely manage large and complex projects. The main features of Slack Connect Spaces are designed to allow Slack users to:

collaborate at scale by bringing together an unlimited number of partners into a space for cross-company collaboration.
minimize admin hassle with flexible organization and invite options that allow teams to self-organize based on project needs.
boost cross-company productivity by bringing all your tools together—such as automation, AI, lists, canvases, and huddles—and organizing your knowledge in one centralized place.
enable cross-company teams to create their own channels and work streams and to onboard and orient new team members.

Discovery API and Slack Connect Spaces

The discovery.enterprise.info API method returns both Slack Connect Spaces and internal workspaces.

The Discovery API provides the ability to capture content in all Slack Connect Spaces, and the permissions model mirrors the current implementation for Slack Connect shared channels.

Slack Connect Space channels will appear the way other channels do, and similar to Slack Connect, Slack Connect Spaces have author-aware, policy-based capabilities.

Object visibility

When calling as the host organization of a shared space, the following will be returned:

All channels
All messages
All files
All canvases

When called as an away organization of a shared space, the following will be returned:

All public channels
Private channels with at least one active member from the away organization
Files and canvases visible to at least one member from the away organization

Enterprise Discovery API methods

A new boolean parameter called internal_teams_only has been added to the discovery.enterprise.info API method, which by default is false and includes shared spaces. To exclude shared spaces, pass internal_teams_only with a value of true.

Conversation & message Discovery API methods

In general, all of the discovery.conversations.* and discovery.chat.* API methods will expect the team parameter, where applicable, to be passed in as the shared space team ID (starting with "T"). For the discovery.conversations.history API method, the team field in the output for a given message from a space conversation will be the Enterprise ID (starting with "E") of the posting user, if the user is from an Enterprise organization. Otherwise, it will be a team ID (starting with "T") for their non-Enterprise home team. We support E-encoded Enterprise IDs in the team parameter in the discovery.user.info API method.

Draft Discovery API methods

Use the top-level E-encoded Enterprise ID (or T-encoded team ID) of the calling organization or team in the discovery.drafts.list API method, and shared space drafts will be included in the response. If the team is a shared space team ID, team_not_found will be returned.