Connect Your Discord Server
Add the verified Subscriby app to the server you manage, the permissions it asks for, the role to drag, and the settings and actions the Connectors page offers afterwards.
Connecting Discord to a project means adding the Subscriby app to one of your servers. The app is Discord's own idea of an integration: it lives in the server with a role of its own, and everything it does, from giving a role to posting a broadcast, is bounded by that role's permissions and its position in the role list.
There is nothing to type. The dashboard sends you to Discord's own authorisation page, you pick the server, and you come back connected.
What you need
- A Discord server where you hold the Manage Server permission (the server owner always does).
- A Subscriby project. One server connects to one project; a second server is a second project.
- A Subscriby account whose Discord identity is linked, or none yet: the account you authorise from is linked as yours on the way in when you hold none.
Add the app to a server
Open the project's Connectors page
Pick the project in the top-left project picker and choose Connectors in the sidebar. Press Browse Marketplace, open the Discord card and press Connect to a project. Discord appears in the project's list as Pending.
Choose Connect
On the Discord row, open the ⋯ menu and choose Connect. The dialog, Connect Your Discord App, lists the four steps and asks for nothing else. Press Connect.
Continue on Discord
The dialog now shows Continue on Discord and waits (Waiting for Discord to send you back…). Press it: Discord's authorisation page opens in a new tab. Pick the server you manage from the Add to server list, review the permissions the app asks for, and press Authorise.
You must be signed in to Discord in that browser as an account with Manage Server on the server you pick. The list only offers servers where you hold it.
Come back
Discord sends you back to the project's Connectors page in that tab, and the dialog you started from updates on its own as well: the row turns Connected, the project header gains the server's name, and the Discord account you authorised from is linked to your creator account if you held none.
Drag the Subscriby role
In your server, open Server Settings → Roles and drag the Subscriby role above every role you are going to sell. Discord lets an app manage only the roles below its own; a role above it cannot be given or taken away, and the doctor will tell you so by name.
The permissions the app asks for
| Permission | Why the app needs it |
|---|---|
| Manage Roles | To give a member the roles their plan includes and take them back when access ends. |
| Manage Channels | To make the role behind a gated channel see it, and to build the members area. |
| View Channels, Read Message History | To read the channels it gates, the mirrored channels and the support threads. |
| Create Invite | To mint a single-use invite for a member it cannot add directly. |
| Kick Members | To remove a member when a server plan ends and you chose removal. |
| Send Messages, Embed Links, Attach Files, Use External Emojis, Mention Everyone | To post broadcasts in your announcement channel, mentioning the plans' roles, and to copy mirrored posts. |
| Create Public Threads, Create Private Threads, Send Messages in Threads, Manage Threads | To open one support thread per member in your forum and answer inside it. |
| Manage Events, Create Events | To put pass windows on the server's event calendar and keep them in step. |
Not asked for: Administrator, Ban Members, Manage Server, Manage Webhooks, Moderate Members. The app bans nobody and changes nothing about the server itself.
Leave every box ticked
Discord's page lets you untick a permission before you authorise. The connect is refused on the spot when one is missing, naming it: give the Subscriby role that permission in Server Settings → Roles, or press Connect again and leave every box ticked. Someone editing the app's role later is the usual way the connector stops working afterwards; the health probe reports it as Permissions trimmed and names what is missing, and giving the permissions back clears it at the next probe.
Settings
Edit settings on the Discord row opens the connector's own settings. Two of them are picks from your server's channels, read live from Discord:
| Setting | What it does |
|---|---|
| Welcome new members with the plans | On by default. A member who joins the server without a membership is sent the plans once, in a direct message. |
| Pass windows as server events | Whether a window of access becomes a Discord scheduled event: No events, Voice and stage channels only (the default) or Every place on sale. See Pass windows as events. |
| Support forum | The forum channel each member conversation opens a thread in, when the project relays support into a forum. Reply inside the thread to answer. See Running your server. |
| Announcement channel | Where a broadcast is posted, mentioning the roles of the plans it is for. Without one, broadcasts go out as direct messages. |
Your server's own settings live in Discord: its name, icon, channels and the order of its roles are set in Server Settings, and the settings card offers Open the server to get there.
Actions
Under the settings, the Discord row offers three actions. Each runs after a confirmation, and each is
also reachable from the API, the apps and /subscriby-admin:
- When server access ends — what happens to a member whose plan for the whole server ends: Keep the member in the server and remove the roles their plan gave (the default) or Remove the member from the server. A member who still pays for a role or a channel on that server is never removed by a server plan ending.
- Set up a members area — creates a private category with
#members,#announcementsand a voice lounge, a role that sees them, and puts that role on sale as the first place; broadcasts post into#announcementsfrom then on. Name it as you like (Members unless told otherwise); a role already called that is refused before anything is made. Running your server has the detail. - Pass windows as server events, per place — one place's own answer when the server default is not what it needs.
Managing a connected server
Verify and the doctor
Verify asks Discord about the server and the app's role at once; the hourly probe does the same on its own. Run Doctor goes further and asks about every place the project sells: a role the app can no longer manage, a channel it can no longer see, a place Discord no longer has. Each line comes with the fix, and the common one is Drag the Subscriby role above ….
What the health states mean
| State | What happened | What to do |
|---|---|---|
| App removed | The app was removed from the server, or the server is gone. | Add it back from the Connectors page; members keep their memberships and are given their roles again. |
| Permissions trimmed | Someone edited the app's role. | Give it back Manage Roles, Manage Channels, Create Invite and Kick Members, and drag it above the roles you sell. |
| Token refused | Discord refused the app itself. | Nothing on your side changed; this is Subscriby's to fix. |
| Discord unreachable | Discord could not be reached or answered with an error. | Usually clears on its own; the next check will tell. |
Reconnect
Reconnect runs the same authorisation again. Use it after the app was removed from the server: pick the same server on Discord's page and the app is back, with every place and member as they were. A server that another project already connected is refused; the same project reconnects freely.
Disconnect
Disconnect makes the app leave the server. Nothing in Subscriby is deleted: resources, plans, members and identities stay, and the roles members hold stay as Discord has them, because the app is no longer there to change them. Connect again at any time; the roles are reconciled against the ledger soon after. Uninstall is the bigger step, described on Connectors.
Common problems
"Drag the Subscriby role above …" — the role you sell sits at or above the app's role in the role list. Open Server Settings → Roles and drag the app's role up. Nothing else changes.
The channel I sell is invisible to the app — a channel the app cannot see cannot be gated. Give the app's role (or the app directly) View Channel on it, or move it out of a category that hides it.
Members are not added, only invited — the app adds a member to the server by itself only when the member connected their Discord account on the portal; everyone else receives a single-use invite. See Integration.
"The app needs a text channel it can create invites in" — invites are minted on the server's system channel, or the first text channel the app can see. A server with neither has nowhere to invite into; give the app a text channel.
The server is already connected to another project — one server, one project. Disconnect it there first, or use another server.
I installed from the wrong Discord account — the account you authorise from is linked to your creator account only when you held none; otherwise nothing changes. Linked accounts are managed under Settings → Security → Linked accounts.
Related
- Integration — what the app does with the roles once it is in.
- Running your server — the members area, broadcasts, support and alerts.
- How the app stays connected — the live connection and what to check when it goes quiet.
- Connectors — the generic install, verify, disconnect and uninstall flow.
How is this guide?
Last updated on
Create Your Account with Discord
Sign up with Continue with Discord or by email, link your Discord account, and add the app to your first server in a few minutes.
Sign in with Discord
How Continue with Discord works, what Discord shares, how to link or unlink an account, and why email and passkeys stay available.