Read-only Slack access
The Slack app requests read-only scopes for approved channels. The hosted ingestion path is channel-focused and does not ask for broad message-writing or impersonation capabilities.
Read docs →Slackscraper is designed around approved channel scope, tenant/workspace boundaries, read-only Slack permissions, audit events, deletion handling, and verifiable exports.
The Slack app requests read-only scopes for approved channels. The hosted ingestion path is channel-focused and does not ask for broad message-writing or impersonation capabilities.
Read docs →Tenant and workspace keys, authorization checks, credential scopes, and operational review guard against cross-workspace access and stale result expansion.
Message deletions create tombstones. Stale event replay cannot resurrect deleted content, and old result handles are invalidated after deletion changes.
JSONL exports include manifest metadata, record counts, SHA-256 checksums, current-state filtering, access-profile scoping, and chain-of-custody fields.
Credential lifecycle, access profile edits, deletion requests, exports, job replay, and operations metrics emit audit events with sensitive values redacted.
Deployment reviews can include configuration checks, redacted diagnostics, and evidence that secrets and message bodies stay out of shared support materials.