Connect your community to your Discord server, and keep the two in step without anybody doing it by hand.
Roles that follow your groups
Map an Invision Community group to a Discord role and members get it automatically — when they connect their account, when you promote them, and on a regular sweep that catches anything missed while Discord was unreachable. Secondary groups count too.
It only ever touches roles you mapped. Colour roles, bot roles and anything a moderator handed out inside Discord are left exactly alone.
The reverse matters as much: ban somebody, flag them as a spammer or delete them, and the roles come off straight away. For a lot of communities the Discord server is the thing actually being revoked.
Names that match
Each member's Discord nickname is set to their display name here, so people are recognisable in both places and nobody can quietly impersonate a regular.
Announcements, from anywhere in the suite
Send new content to a Discord channel — forum topics, replies, gallery images, calendar events, downloads, blog entries, products, and every Pages database you have, including their comments and reviews. Around 25 content types on a normal install, and it finds new ones by itself rather than working from a list that goes stale.
Filter by category, by author, or by a minimum post count so brand-new accounts cannot broadcast to your server. Rich embeds, or plain messages if you prefer Discord's own link previews.
Content held for moderation is never announced — it goes out if and when it is approved, and not before.
Moderator reports in Discord
When a member reports something, your moderators can hear about it in a channel of their own, in a colour that stands out from ordinary announcements. Reports never travel through the normal rules, so they cannot end up somewhere public by accident.
Invites you control
Create invite links in the AdminCP, restrict them to chosen groups, and hand them out instead of an ordinary Discord invite. Optionally make people ask first: a request goes to your staff, who approve it once or for good, and the member is added to the server immediately.
Invites only mean something if your Discord server has no ordinary invite links of its own. The setup guide covers this — it is the one step people miss.
Sign in with Discord
Switched on for you when setup finishes. Members connect once and everything else follows from that.
A widget for your sidebar
Discord's live widget in either theme, or any of its four banner badges, optionally with a join button pointing at one of your own invites.
Moving from another Discord app?
The expensive part of switching is not settings — those take minutes. It is the members who already connected their Discord account, because most will never do it a second time, and a community that loses those links loses the role syncing it was paying for.
So this reads your database, finds another integration's connected accounts by the shape of the data rather than by guessing at table names, shows you exactly how many it found, and imports them only when you say so. It works whichever application you are leaving.
Set up in two steps
Paste three values from your Discord application, then pick your server from a list. Nothing asks you to switch on Developer Mode or copy an eighteen-digit ID by hand.
The bot asks for permission to manage roles and nicknames, create invites and post messages. It never asks to be an administrator of your server.
When something goes wrong
Every call and every sync is logged with its reason, so “it stopped working” is a question you can actually answer. Secrets are never written to it.
What's New in Version 1.0.4
Released
The AdminCP database check no longer reports this app
Invision Community's Support → Database screen could report that this
application's tables "have some problems", and offer to fix them with a long list of queries that
create a copy of each table, move the data across, DROP the original and rename the
copy.
Nothing was actually wrong with your database, and those queries did not need to be run. The tables were correct. What was wrong was this application's description of them: its index definitions omitted one optional field, so the checker compared the description against reality, found them different, and offered to rebuild the table to match a definition that was already true.
This release corrects the description. The check now passes and nothing is altered in your database — no table is copied, dropped or renamed.
If you already ran the suggested queries, no harm done: they rebuild each table to exactly what it was.
Nothing else changes in this release.
You may only provide a review once you have downloaded the file.
There are no reviews to display.