➕ Adding Fren One to Discord

Fren One for Discord is set up entirely from the webapp: you connect your Discord account, pick the servers you admin, invite the agent, and assign each server to a workspace. Once a server is connected, its full configuration dashboard unlocks.

Before you start

• You need admin permissions on the Discord server you want to connect: the wizard only lists servers where you're an admin.
• Decide which workspace should own the server. A workspace groups your channels, team, and settings; one workspace can hold several servers and platforms. See the Workspaces docs for how workspaces, teams, and billing fit together.

Connect a server

1. In the Fren One webapp sidebar, under Channels, select Connect a channel (it's also in the workspace switcher's menu). If you're starting fresh, open the workspace switcher and select Create or join a workspace instead, or Add workspace if you're not on any workspace yet: the same wizard runs with a workspace-naming step first.

2. On the Platform step, choose Discord. If your Discord account isn't linked yet, the wizard shows what it will ask Discord for (reading your username and profile, and seeing the servers you belong to) and sends you through Discord authorization via Continue with Discord.

3. On the Select step, pick the servers to manage. Each server shows a status badge:

   Badge	Meaning
   Already connected	Managed in your current workspace.
   In another of your workspaces	Managed elsewhere in your account: open it from that workspace.
   Managed	Active in a workspace you're not a member of. Ask that team for an invite, or verify from the dashboard as one of the server's admins, which joins you as a Channel admin (see Joining a Workspace).
   Claimable	Previously connected and now available to claim.
   Agent already added	The agent is in the server but it isn't attached to a workspace yet.
   Agent removed	The agent was removed from a server in one of your workspaces: use Re-add Fren One to re-invite it.

4. On the Add Agent step, select Invite agent next to each server. A Discord popup asks you to authorize the agent for that specific server. Fren One detects the agent automatically once it joins: no refresh needed.

5. Assign each detected server to a workspace (or pick New workspace to create one inline) and review.

6. On the Privacy step, name any Discord channels the agent should never read. This is optional and skippable, and it's the cheapest moment to do it: nothing has been read yet, so ignoring a channel now costs nothing. Setting it later still works, but it erases everything already read from that channel. See Ignored Channels.

Administrator permission

The invite installs the agent with Discord's Administrator permission. This is what lets moderation, role management, ticket channels, backups, and protection features work without per-permission setup. If you customize the agent's permissions afterwards, individual features can stop working: see the permissions table below.

After the wizard completes, the server appears in your workspace sidebar under Channels (the Done step also offers Go to channel). Select it to list its pages: Overview, then every feature area. A feature's sub-areas are tabs at the top of its page.

Who can see and configure the server

Reading and configuring are two different questions.

Anyone on the workspace can read the server's data. Its overview is open to every workspace member, and its analytics, members list, inbox, reports, Ask AI and audit log are the workspace pages filtered to this server. If you're not verified on that server, the page shows a "Viewing as a workspace member" banner with a Verify to manage button, and the configuration pages stay locked. A Channel admin, someone who joined by verifying on a server and holds no workspace role, sees only the channels they're verified on.

Configuring the agent and moderating requires being a verified admin of that specific server. This applies to everyone, the workspace Owner included.

• Discord admins in the workspace verify with one click: the dashboard shows a Verify to manage screen, checks your Discord permissions live, and unlocks the server.
• Members without Discord admin can still be given access: add one of their roles under Agent Settings → Agent admin roles. Holding an agent admin role lets them verify and manage the agent: both from the webapp and in Discord.
• Verification has to stay fresh. Your admin status is re-confirmed with Discord on a rolling basis, and it must have been confirmed within the last 72 hours to keep unlocking configuration.
• If the agent is removed or unreachable, Fren One can't confirm anything, so access pauses rather than continuing on stale information. You'll see a Re-verify access prompt, and you drop back to the read-only workspace member view of the server. You're not removed from the workspace, and the pause lifts as soon as your status is confirmed again or you re-verify manually.

The Knowledge Base is workspace-level

A server has no Knowledge Base page of its own. The Knowledge Base is one of the workspace rows in the sidebar, shared by every channel in the workspace, and every workspace member can read it.

Role hierarchy

Discord only allows the agent to manage roles below its own highest role. Keep the Fren One role above every role it needs to grant, remove, or quarantine: reaction roles, auto roles, XP role rewards, and quarantine actions all depend on this.

tip

Drag the Fren One role near the top of your role list, directly under your admin roles, and you'll rarely hit hierarchy problems.

What the agent uses its permissions for

The default install (Administrator) covers everything. If your server policy requires trimming permissions, these are the features each permission powers:

Permission	Used for
Manage Roles	Verified role, auto roles, delayed roles, reaction roles, XP role rewards, quarantine.
Manage Channels	Ticket channels and categories, automatic slowmode, backup restore.
View Channels, Send Messages	Welcome/goodbye messages, scheduled messages, embeds, AI replies, ticket panels.
Embed Links, Attach Files	Rich embeds, verification embeds, welcome cards, transcripts.
Manage Messages	Filters, word blacklist, trigger cleanup, spam handling.
Timeout, Kick, and Ban Members	Warns, reports, vote ban, anti-raid, blacklist rules, AI moderation actions.
Manage Webhooks	Translation modes that post as the original author.
Create Invites	Invite reward links.
View Audit Log	Attributing native Discord moderation actions in the mod log.

When the agent lacks a permission or the target role sits above it, the action fails safely: it is not recorded as a success in the mod log.

First configuration checklist

• Turn on Bot Protection and post the verification embed.
• Configure welcome and goodbye messages.
• Set your Mod Log destinations so every action is visible to staff.
• Add agent admin roles in Agent Settings so your team can manage the server.
• Review role hierarchy before enabling role rewards or quarantine actions.
• Run a quick test with a non-admin account.

Related features

• 🛠️ Agent Settings: Agent admin roles, language, and custom branded bots
• 👋 Onboarding: The first experience new members get
• 🛡️ Server Protection: Backups and anti-nuke monitoring from day one