Skip to main content

➕ 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 project. 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 project should own the server. A project is a workspace that groups your communities, team, and settings; one project can hold several servers and platforms. See the Projects docs for how projects, teams, and billing fit together.

Connect a server​

  1. Open the Fren One webapp and select Add Community (or Create Project if you're starting fresh — the same wizard runs with a project-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:

    BadgeMeaning
    Already connectedManaged in your current project.
    In another of your projectsManaged elsewhere in your account — open it from that project.
    ManagedActive in a project you're not a member of. Ask that team for an invite, or verify from the dashboard as one of the server's admins.
    ClaimablePreviously connected and now available to claim.
    Agent already addedThe agent is in the server but it isn't attached to a project yet.
    Agent removedThe agent was removed from a server in one of your projects — 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 project (or create a new project inline), review, and finish.

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 project. Open it and use the Agent Configuration sidebar to reach every feature area.

Who can configure the agent​

Access to a server's configuration requires being a verified admin of that specific server — being in the project isn't enough on its own.

  • Discord admins in the project 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 is re-checked periodically. If the agent is removed or unreachable, access pauses with a Re-verify access prompt until the agent is back and your status is confirmed.

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:

PermissionUsed for
Manage RolesVerified role, auto roles, delayed roles, reaction roles, XP role rewards, quarantine.
Manage ChannelsTicket channels and categories, automatic slowmode, backup restore.
View Channels, Send MessagesWelcome/goodbye messages, scheduled messages, embeds, AI replies, ticket panels.
Embed Links, Attach FilesRich embeds, verification embeds, welcome cards, transcripts.
Manage MessagesFilters, word blacklist, trigger cleanup, spam handling.
Timeout, Kick, and Ban MembersWarns, reports, vote ban, anti-raid, blacklist rules, AI moderation actions.
Manage WebhooksTranslation modes that post as the original author.
Create InvitesInvite reward links.
View Audit LogAttributing 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.

On this page