TABLE OF CONTENTS
Overview
The Slack Source delivers Stack Internal Trust workflow messages in Slack and handles Slack interactions. It checks incoming Slack requests before acting on them. For outgoing messages, it uses the approved Slack access assigned to the source. The source handles the selected recipient and message details needed for each workflow. This keeps Slack message handling controlled while allowing Trust workflows to reach the people and channels selected for them.
Request checks
The source checks Slack requests before Stack Internal handles an interaction. This check confirms that the request came through the expected Slack connection. Slack-specific request handling stays within the source, so other parts of Stack Internal do not need to process Slack request details directly.
Message delivery
The source delivers Trust workflow messages to Slack using its approved Slack access. It handles the target person or channel and the message prepared for delivery. The source also accounts for Slack delivery limits and can report a delivery failure for follow-up. These controls keep message delivery within the approved Slack connection.
Information handling
The source handles the Slack message, interaction details, and selected recipient needed for a workflow. These details are used to process an interaction or deliver a message. The source keeps Slack-specific information within the part of Stack Internal that manages the Slack connection.
FAQ
Data access, privacy, and storage
What customer data can the Slack Source access or retrieve?
The Slack Source handles the message text, interaction details, and Slack recipient needed for a Trust workflow. It uses those details to respond to a Slack interaction or send a workflow message to the selected person or channel.
Does the provider have visibility into data processed by the Slack Source?
Slack receives the workflow messages that Stack Internal sends through the source. Slack also provides the interaction details that the source checks before handling a Slack request. The connection is limited to the information needed to send or respond to a workflow message.
Access and permissions
How does the Slack Source authenticate users, services, or client applications?
The source checks incoming Slack requests before handling them. For outgoing messages, it uses the approved Slack access assigned to the source. Together, these controls verify incoming interactions and limit message delivery to the source's authorized Slack connection.
What permissions does the Slack Source need to access internal or external systems?
The source needs the approved Slack access required to deliver Trust workflow messages. It uses that access to send messages to selected Slack recipients. Incoming Slack interactions are checked before Stack Internal processes them.
Security and audit controls
How does the Slack Source prevent unauthorized access, data exfiltration, or unauthorized write actions?
The source checks incoming Slack requests before it handles an interaction. It uses assigned Slack access only for message delivery through the approved connection. This keeps incoming request handling and outgoing Slack messages within the source's controlled workflow.
Additional security controls
How are tokens, credentials, or secrets stored, rotated, and revoked?
The Slack Source retrieves each organization's signing secrets from protected secret storage. It can use both the current and previous signing secret during a short transition period, which supports orderly secret rotation. Slack bot credentials and other service credentials are also supplied through protected deployment secret storage rather than placed in application code.
Integration and API usage
How is the connection established between the Slack Source and internal or external systems?
The source receives Slack interactions through its Slack connection and sends Trust workflow messages through that same connection. It checks incoming requests before handling them and uses approved Slack access when delivering a message.
Does the Slack Source support read operations, write operations, or both?
The Slack Source supports both. It receives Slack interaction details for Stack Internal to handle, and it sends Trust workflow messages to Slack. It also accounts for Slack delivery limits when handling outbound messages.