Slack App Setup for SlackVault - Scopes and OAuth Flow

Creating your Slack appSlackVault reads your workspace through a Slack app that you create and own, which is what keeps the credentials in your hands. You grant it read-only scopes covering the conversation types you want archived, and the OAuth code exchange happens in a Cloudflare Worker so the client secret is never shipped in the website or extension bundle. Fewer scopes means less coverage, so choose deliberately.What this covers

Channel scopes cover public channel history and metadata.

Group scopes cover private channels you are a member of.

Direct and multi-party message scopes cover one-to-one and group conversations.

User scopes resolve author names and email addresses.

File and team scopes cover attachments and workspace metadata.

What SlackVault does not do

Every scope is read-only. The app cannot post, edit or delete anything in Slack.

Workspaces with app approval enabled need an administrator to approve the app first.

Scopes cannot retroactively widen an archive; conversations synced under narrower scopes stay as they were.

SlackVault documentation

Getting started with SlackVault

Configuring your Firebase project

Data security

Written by Ahsan Mahmood. Last updated 2026-07-21.https://slackvault.aoneahsan.com/docs/slack-app-setup