Slack
The following table(s) contains detailed examples of the metadata fields available from the Slack API endpoints Worklytics leverages. In order to pseudonymize and sanitize PII and other potentially sensitive data, Worklytics provides access to a Data Loss Prevention (DLP) Proxy, which allows customers to pre-filter metadata, within customer infrastructure, before it is sent to Worklytics for processing.
These are the fields Worklytics recommends but the Worklytics DLP Proxy provides full field-level control and therefore any field may be removed or sanitized.
Field descriptions are taken from third party API documentation, these are maintained on a best effort basis and Worklytics can not guarantee their indefinite accuracy. Please refer to the source API site for the most up-to-date documentation.
How to read the "DLP Proxy" column in the table(s):
🔴 This field is completely redacted by the DLP Proxy
⭕ This field is transformed, usually partially redacted
🟡 This field is "pseudonymized" by the DLP Proxy: only a SHA256 hash of its value is sent to Worklytics; never the value itself
To see only the fully sanitized version of this document, click here.
Worklytics requires access to the following API primary endpoints:
Conversation
API docs: https://api.slack.com/enterprise/discovery/methods
DLP Proxy docs: Slack
Message
API docs: https://api.slack.com/enterprise/discovery/methods
DLP Proxy docs: Slack
Enterprise
API docs: https://api.slack.com/enterprise/discovery/methods#enterprise_info
DLP Proxy docs: Slack
User
API docs: https://api.slack.com/enterprise/discovery/methods
DLP Proxy docs: Slack
Last updated
