CYBBACK| for Slack
Quick User Guide

Your first Slack backup
in under 15 minutes.

From sign-up to a fully encrypted, restorable snapshot of your Slack workspace - channels, messages, threads, files, users and user groups. This guide walks you through every step.

AudienceIT admins & compliance leads
Reading time~ 10 minutes
Setup time~ 15 minutes
VersionEN - 2026
What you'll learn

6 steps to a production-ready backup

1
Get started

Sign up - trial or paid licence

CYBBACK offers two ways to get started. Both unlock the full Slack feature set.

Option A - Free trial

  1. Open cybback.com/essai-gratuit.
  2. Fill in your work email, company and a password. Click Start free trial.
  3. Confirm via the verification email.
  4. On the trial selection screen, pick Slack. Your trial workspace is provisioned instantly.
Painless onboarding

Trial accounts get the full Slack feature set - encryption, BYOB, scheduling, bot-annotated restore. Switch to a paid plan at any moment without losing data.

Option B - Paid licence

  1. Go to cybback.com/tarifs and pick the Slack plan that matches your workspace size.
  2. Click Subscribe. Stripe Checkout supports cards, SEPA and invoicing on annual plans.
  3. Your licence is active immediately - visible under Account → Subscription.
2
Create the Slack app

Create an internal Slack app + required scopes

CYBBACK connects to your Slack workspace via an internal Slack app that you own and control. No third-party OAuth - the Bot Token stays in your CYBBACK vault.

Create the app

  1. Open api.slack.com/apps → click Create New App.
  2. Choose From scratch. Name it CYBBACK Backup, select your workspace.
  3. Click Create App.

Add OAuth scopes

In the left sidebar go to OAuth & Permissions → Scopes → Bot Token Scopes. Add all of the following:

channels:read channels:history, channels:join groups:read groups:history users:read usergroups:read files:read team:read chat:write channels:manage, groups:write files:write

Blue scopes are only needed for restore (files:write is used to restore files). Read-only backup works without them, but we recommend adding them upfront.

Install the app and copy the Bot Token

  1. Scroll up in OAuth & Permissions and click Install to Workspace.
  2. Review the permissions and click Allow.
  3. Copy the Bot User OAuth Token (starts with xoxb-). It will not be shown again after you leave the page.
Workspace Admin required

Installing a Slack app requires Workspace Admin or Owner permissions. If you don't have them, ask your IT admin to perform steps 2 and 3 - they only need to share the Bot Token with you.

3
Connect to CYBBACK

Paste the Bot Token + configure coverage

CYBBACK validates the Bot Token, discovers your channels and lets you tune what gets backed up.

Paste the token

  1. Open app.cybback.com/dashboard/slack-backup → Configuration.
  2. Paste the xoxb- token and click Validate. CYBBACK calls auth.test to confirm the token works and fetches your workspace name and channel list.
  3. The Bot Token is encrypted (AES-256-GCM) and stored in the CYBBACK vault.
app.cybback.com/dashboard/slack-backup
Dashboard
Configuration
Bot TokenEncrypted at rest

Internal Slack app Bot Token (xoxb-).

 ✓ acme.slack.com - 312 channels discovered
Backup coverage
Public channelsAll public channels accessible by the bot
Private channelsOnly channels the bot has been invited to
Shared filesDownload files attached to messages

Invite the bot to private channels

The Slack API does not expose private channel content to bots unless the bot has been explicitly invited. For each private channel you want backed up:

/invite @CYBBACK Backup
Pro tip: batch-invite via admin panel

Workspace Owners can use Slack Admin → Apps → CYBBACK to install the app in all private channels at once, avoiding the need to type /invite in each channel individually.

4
Bring Your Own Bucket

Use your own S3-compatible storage

Want full data sovereignty? Point CYBBACK at your S3-compatible bucket - AWS S3, GCS, Scaleway, OVH, Wasabi, MinIO. Your data, your provider, your region.

Provision the bucket

  1. In your S3 provider, create a private bucket (no public access, versioning recommended).
  2. Create an access key / secret key with permissions limited to that bucket.
  3. Note your endpoint URL and region.

Configure CYBBACK

  1. Open Dashboard → Storage.
  2. Select My own S3 storage.
  3. Fill the form, click Test connection, then Save.
Dashboard → Storage
S3 ConfigurationEncrypted at rest
 

Optional: enable encryption at rest

Toggle Encrypt backup files in Storage settings. CYBBACK applies AES-256-GCM to all message JSON and downloaded files. The manifest is never encrypted so the dashboard can display summaries without decrypting.

5
First backup

Run your first backup

You're now fully configured. Time to run your first Slack snapshot - manually for instant peace of mind, then schedule recurring runs.

Manual backup

  1. Go back to the Dashboard tab.
  2. Click Run backup now. The job appears with status pending, then running.
  3. Progress is streamed live: Bot Token validated, channels enumerated, messages fetched, files downloaded, manifests saved.

Schedule automatic backups

  1. From Dashboard → Schedules, click New schedule.
  2. Service: Slack. Frequency: Daily / Weekly / Custom (cron).
  3. Pick a window (e.g. 03:00 Europe/Paris) and click Save.

Track your backups

First run takes longer

The initial backup captures the full history of every channel since the workspace was created. For large workspaces (1M+ messages), this can take 30–60 minutes. Subsequent incremental runs are much faster - only new messages since the previous run are fetched.

6
Restore & Export

Restore messages - bot-annotated & granular

CYBBACK restores from any previous Slack snapshot. Recreate a channel, replay its message history, or export a ZIP for compliance - all from the same interface.

The 3-step restore flow

  1. Selection. Open the snapshot, browse the channels and date ranges, tick what you want to recover.
  2. Options. Choose your safety net:
    • Dry-run - simulate, no Slack API write calls.
    • Target channel - restore into the original channel name, a new one, or a temporary -restored suffixed channel for review before cutover.
  3. Execution. The worker recreates the channel (if needed), then calls chat.postMessage for each message. Each message is annotated: "Originally posted by @alice on 2025-03-14 09:42". Files are re-uploaded.
Channel creation may be restricted by your workspace

If restore fails with restricted_action on conversations.create, your Slack workspace reserves channel creation (especially private channels) to admins - no OAuth scope changes this. Ask a Slack admin to allow members to create channels (Workspace settings → Permissions → Channel Management), or restore into a public channel instead.

Dashboard → Slack → Restore
1. Selection
2. Options
3. Execution
Restore options#engineering-alerts · 4 280 messages
Dry-runSimulate without posting to Slack
Re-upload filesAttach files to restored messages
 

Export for compliance (GDPR / litigation)

Restored messages appear as the CYBBACK bot - not the original user

The Slack API does not allow one user/bot to post as another. Restored messages are always posted by the CYBBACK bot with an annotation naming the original author. This is a hard Slack API limitation, not a CYBBACK constraint.

Direct messages are not backed up

The Slack API does not expose DMs to bots. CYBBACK only has access to channels (public and private ones the bot was invited to). DMs are outside scope - this is an intentional Slack API design choice.

You're all set.

Need help? Our team replies within one business day on every plan.

Contact support →