Setup guide

Echo setup

Copy one member's messages into another channel, and why the view role decides what an echo can see.

What it is for

Echo watches a specific member and pastes what they post into a channel you choose. The usual reasons:

  • Mirroring announcements from a founder or lead into a channel that members with a particular role can read
  • Collecting one person's calls or signals into a single feed rather than leaving them scattered across channels
  • Giving a role visibility of messages posted somewhere they cannot see

Setting one up

Each echo has four fields.

Title

A name for the echo. Only visible to you, on this page — it exists so a server with several echoes running is manageable.

User ID

The member whose messages get copied. Enable Developer Mode in Discord's advanced settings, then right-click the member and choose Copy User ID.

Paste channel

Where the copies go.

View roles

The important one, and the one worth reading twice: ScoutBot only copies messages from channels that this role can already read the history of.

That is a deliberate safety property rather than a limitation. Without it, an echo would be a way to lift messages out of a private channel and paste them somewhere the original audience never agreed to — so the role you pick here defines the boundary of what the echo is allowed to see.

Pick a role that genuinely has access to the channels you want mirrored. If an echo seems to be doing nothing, this is almost always why.

Turning it on and off

The switch at the top of the page stops all copying. Your configured echoes are kept, so it works as a pause.

Free

Echo is free on every server.

Protect your moderators free

Impersonation alerts for up to three protected names, with no card and no time limit. Pro covers your whole mod team automatically and adds avatar image matching.

Add ScoutBot to your server