🙈 Ignored Channels

Ignored Channels keeps private Discord channels, such as leadership, HR or staff channels, away from the agent. From the moment a channel is ignored, the agent stops reading and storing anything from it. Adding a channel also erases the content already stored from it that can be traced to that channel; the purge report lists older records that couldn't be traced and artifacts, such as reports or knowledge base entries, that you need to review.

This is the privacy boundary for your whole workspace

Every member of a Fren One workspace can read the workspace's analytics, reports and Ask AI, so the ignore list is the only thing keeping a private Discord channel's content from them. If a Discord channel shouldn't be readable by everyone on the workspace, ignore it.

Configuration

Open your workspace in the Fren One webapp.
In the sidebar under Channels, select the Discord server you want to configure. Its pages open beneath it.
Select Agent Settings, then the Ignored Discord Channels tab.

Who can see and change the list

Everyone verified on the server can see the list. It's read-only for most people, with a note saying so: "You can see what is ignored here, but only the workspace owner or a workspace admin with a verified Discord admin account can add or remove Discord channels."

Changing the list needs both the Owner or Admin role in the workspace and an active verified Discord admin status on that server.

Every change is written to the audit log on both sides: your Fren One workspace's audit log and the server's own configuration history.

Ignoring a channel

Select Add a Discord channel or category and pick from the list. You can ignore categories, text and announcement channels, voice and stage channels, and forum and media channels. Threads never appear in the picker because their parent already covers them.

Ignoring is inherited, two levels deep:

Ignoring a category covers every channel and thread inside it.
Ignoring a channel covers that channel and its threads.

A server can hold up to 600 ignored entries.

Outbound messages still get delivered

Ignoring stops the agent reading, not the agent writing. Anything you've set Fren One up to send to that channel keeps working: alert routing, the mod log, scheduled messages, feeds, ticket panels, translation targets. The agent posts there and simply never looks at what else is said.

Some channels can't be ignored

If a feature you've switched on needs to read a channel, ignoring it would silently break that feature, so Fren One refuses and tells you which feature is in the way: "A feature you have switched on needs to read these Discord channels. Turn it off for them first, then ignore them."

Feature	What it needs to read
Support tickets	Ticket categories, and any channel with a live ticket in it
Reaction roles	The channel each enabled reaction-role panel lives in
Translation rules	The source channel of a rule (the target stays ignorable)
Moderation filters	Channels a filter is scoped to
Word filter	Channels the word filter is scoped to
Automatic slowmode	Channels slowmode monitors
AI leaderboard	Channels the leaderboard tracks
Automations	Channels named in an enabled automation's conditions
Quests	The channel of an active message-post quest
Channel bridge	The origin channel of a live bridge relay

The fix is always the same: turn the feature off for that channel, then ignore it. Exemption lists work the other way round and never block anything, so a channel that a filter skips can be ignored freely.

Adding a channel erases its history

Ignoring a channel destroys what the agent has already stored from it, immediately and unrecoverably. There is no "ignore but keep the history" option, since the kept history would stay readable by the people you're hiding it from.

Adding a channel asks you to type the channel's name to confirm. Before you do, Fren One shows how much is about to go: the number of messages and reactions stored, and how many channels the entry covers. If it can't reach the message store to count, it says so instead of showing zero.

The confirmation spells out what happens:


Destroyed immediately and unrecoverably	Raw messages, reactions, search embeddings, quoted events, ticket conversation content, and the agent's memory of this channel.
Kept	Numbers-only aggregates such as member counts and activity totals. They carry no content. Punishment records (warns, mutes, bans) and ticket workflow records also survive: the conversation goes, the record that something happened stays.
Flagged for your review, never silently destroyed	Admin-edited knowledge base entries, generated reports, and Ask AI chats that may quote the channel. Anything a person has worked on is your call, not ours.

Ignoring is free before anything has been read

The cheapest moment to ignore a channel is before the agent has ever seen it. The Discord connect wizard has a Privacy step for exactly this: "Pick any Discord channels the agent should never read. Nothing has been read yet, so ignoring one now erases nothing." You can change the list later in Agent Settings, but adding a channel then erases everything already read from it.

The purge report

Once the erase finishes, a report lands in your workspace inbox titled "Discord channel history erased". If a store couldn't be cleared, it's "Discord channel history not fully erased" instead, and the job retries automatically.

The report is visible to the Owner and Admins only, unlike most inbox alerts: it lists exactly what was destroyed, which would reveal the hidden channel's shape to anyone else.

Select Show report to expand it. It has three sections.

Erased

Per-store counts of what was destroyed: messages, reactions, quoted events, trending topic samples, agent memory, ticket content, and search embeddings with AI query history. If a store failed, it's named here with a note that the purge will be retried.

Not covered by this purge

Fren One hasn't always recorded which channel every stored record came from, so some older records can't be traced to the channels you ignored. Rather than deleting on a guess, they're left in place and counted here: "They cannot be traced to these channels, so they were left in place rather than deleted on a guess."

Deleted channels and threads that can no longer be traced back to a parent are listed here too, for the same reason.

Needs your review

The artifacts that quote the channel but that a person may have worked on: knowledge base entries, reports, and Ask AI chats. Each links to the page where you can look at it and decide.

Knowledge base entries are grouped by where they came from:

Group	What it means
Built by the agent	Generated from the channel and never edited by anyone on your team.
Edited by your team	Someone worked on it. Review before removing anything.
Unknown origin	Created before Fren One tracked edits, so someone may have written it.

Only the first group gets a one-click Remove action, and eligibility is re-checked at the moment you press it: anything edited since the report was generated is kept for your review instead of deleted. Every removal is written to the audit log.

Removing a channel from the list

Select Remove on a row and confirm. The agent starts reading that channel again from that moment on.

Removal is forward-only. Nothing from while the channel was ignored is backfilled, and history erased when you added the channel never comes back.