Communication systems often contain conversations for many clients, teams, and topics. Before exposing a communication connection to a Space, limit the connection to the smallest useful set of messages or transcripts.
This keeps the Space’s context relevant and prevents unrelated communications from becoming available to its members, agents, pages, and automations.
Choose the destination Space first
Start with the access boundary. Identify which Space should use the communication data and confirm that its membership matches the people who should be able to read it.
If the same communication system contains data for multiple clients or businesses, use separate scoped connections for their Spaces instead of exposing one broad connection everywhere.
Filter before you expose
Configure the connection’s source scope before exposing it to a Space. Available controls depend on the provider:
Slack
Select only the Slack channels relevant to the Space. Avoid exposing organization-wide or cross-client channels when the Space serves one client or business.
Gmail
Limit included messages using one or more of these criteria:
- Contacts and email domains
- Gmail labels
- Text found in a message’s subject or body
Outlook
Limit included messages using one or more of these criteria:
- Contacts and email domains
- Outlook folders
- Text found in a message’s subject or body
Fathom and Fireflies
Limit meeting transcripts by participant email address or domain. For Fireflies, you can also match text in the meeting title.
When a provider supports a historical import window, select only the period the Space needs.
Review filters carefully before exposing the connection. A broad domain, shared folder, channel, or text rule can include conversations beyond the intended client or business.
What exposure enables
After you expose the scoped connection, its included content can be used by:
- Agents working in the Space
- Chats started in the Space
- Page synthesis and automatic page updates
- Automations that read connected content
- Connection triggers available to automations
The connection’s configured scope remains the boundary. Content excluded by its filters should not become available merely because the connection is attached to the Space.
Account for linked Spaces
A parent Space can read content from its linked child Spaces. This includes communication data made available through a child’s connections.
Before exposing a communication connection to a child Space, review both the child’s direct membership and any parent Spaces that link to it. Do not expose the connection if either audience is broader than the people who should see the included conversations.
Before exposing a communication connection
Confirm that:
- The destination Space represents the correct client, business, or operational area.
- Everyone with direct or linked access should be able to read the selected communications.
- Provider filters include only the required channels, people, domains, folders, labels, meetings, or text matches.
- The historical import window is no broader than necessary.
- The connection owner understands which Space will receive access.
After exposure, review the resulting content before relying on it in pages or automations. Tighten the connection scope if unrelated communications appear. 
