TABLE OF CONTENTS
Overview
Sources link Stack Internal with approved content sources and workplace tools, bringing selected information into Stack Internal so it can be prepared for search and retrieval.
Source connections
Source connections accept approved content and pass it into Stack Internal for preparation and search. The product keeps the resulting knowledge records in its product database and search store. This allows Stack Internal to use connected content in knowledge features while keeping the connection focused on the information needed for that purpose.
Access controls
Connected sources use authenticated access. Stack Internal uses an identity provider to check users and connected applications before protected content work begins. Slack requests receive a separate request check before the product handles them, and message delivery uses the approved access assigned to the connection.
FAQ
Data access, privacy, and storage
What customer data can sources access or retrieve?
Sources handle the content, message details, and account information needed for a connected product feature. A content connection handles approved source content for Stack Internal knowledge features. The Slack connection handles message text and the Slack recipient selected for a Trust workflow message.
Is customer data persisted, transmitted, or copied outside the approved environment?
Content brought into Stack Internal is prepared for search and kept in the product database and search store. The connection handles only the information needed to complete the requested exchange.
Access and permissions
How do sources authenticate users, services, or client applications?
Protected content functions use authenticated access through Stack Internal's identity provider. Slack requests, for example, receive a signature check before Stack Internal handles them. The Slack connection uses approved access for message delivery, which keeps message sending under the connection's assigned permissions.
What permissions do sources need to access internal or external systems?
Each source uses access that matches its connected function. Content sources use authenticated access to add approved content to Stack Internal. The Slack connection uses its assigned Slack access to deliver Trust workflow messages and verify incoming requests.
Security and audit controls
How do sources prevent unauthorized access, data exfiltration, or unauthorized write actions?
Sources apply access checks before protected work begins. Slack requests are checked before they are handled, and Slack message delivery uses the connection's approved access. Content sources use authenticated access when adding approved information to Stack Internal knowledge features.
Additional security controls
What monitoring and audit logging capabilities are available for sources?
Sources are supported by the content-ingestion function, which initializes operational monitoring and reports its health status. It also maintains connector state as part of the managed content connection. These records give Stack Internal operators visibility into whether content collection and synchronization are working as expected.
Integration and API usage
How is the connection established between sources and internal or external systems?
Sources use authenticated access to exchange the information needed for their product function. Content sources bring approved content into Stack Internal for knowledge features. The Slack connection, for example, receives Slack interactions and sends Trust workflow messages back to Slack.