How the Integration Works
What the Discord integration gives you: roles, private channels and server membership granted the minute a member pays, removed when access ends, and reconciled on a schedule, with no code.
The Discord integration turns a membership into roles. A plan grants places; on Discord a place is a role, a private channel or the server itself; and the Subscriby app in your server gives and takes those away as the membership ledger changes. Nobody hands out roles by hand, and nobody checks who has paid.
The one app
Every creator's server is served by the same verified Subscriby app. It joins when you connect the server, holds a role of its own, and acts only within that role: it manages the roles below it, sees the channels it is allowed to see, and posts where it is allowed to post. There is no bot of yours, no token, nothing to host. A creator can never lose the app the way a Telegram bot can be banned, which is why the Disaster Recovery Program keeps no standby app for Discord, only standby places and a relinkable account.
The app is also what recognises you: /subscriby-admin works for the Discord account linked to a
creator who manages the project, and that account is linked when you install or from
Settings → Security → Linked accounts.
The three kinds of place
| Kind | What a member gets | Plans it can be sold under |
|---|---|---|
| Role | The role itself, with whatever the role already unlocks in your server. | One-time, recurring, passes and pass series |
| Channel | A text, voice, stage or forum channel. The app makes one role per gated channel, named after the app and the channel, with a single permission: to see the channel (and connect to it, for a voice channel). Members get that role. | One-time, recurring, passes and pass series |
| Server | Membership of the server. The member is added to the server, or invited in, and stays as long as they pay. | One-time and recurring |
A plan can grant any mix of them, and places on Discord sit beside places on other connectors and manual perks in the same plan. The portal calls a channel a Private channel, so members know they are buying a place and not a mention.
Why a channel is gated through a role
Discord caps how many per-member exceptions a channel can carry, and a role scales to thousands of members. The app creates the role the first time a grant needs it, keeps it with no permission of its own, and gives it one exception on the channel. Delete the role and the app makes a new one at the next grant.
Setup guide
Add the app
Connect the server to the project and drag the Subscriby role above the roles you will sell.
Pick what to sell
On the project's Resources page, link a place: the dialog lists your server's roles (highest
first, without @everyone, integration roles and the app's own), its gateable channels by category,
and the server itself, read live from Discord. Pick one and it becomes a resource. From Discord,
/subscriby-admin gate role, gate channel or gate server does the same through Discord's own
role and channel menus, attaching the place to a plan by name on the way. Or let Set up a members
area build a category, three
channels and a role on sale in one click.
Attach it to a plan
Open the plan and tick the place under its resources. A plan can grant several, and a place can be on several plans.
Share the portal link
Members buy on your project's portal. Share its address, a plan's own link, a Smart Link, or post
/subscriby plans in the server for a list with a Buy button per plan.
Your membership page
The portal is where Discord members buy. They can sign in with Continue with Discord, pay through any payment method you switched on, and connect their Discord account from Account & Recovery → Connected accounts so the app can add them to the server itself. There is no checkout inside Discord: Discord has no in-app payment a membership could settle in, so every slash command that sells hands the member a portal button.
Adding members
When a grant is issued, the app takes the first door that is open for that member:
- Already in the server — the role is given at once. For a server plan there is nothing to give; the member simply holds the membership.
- Connected Discord on the portal — the member authorised the app to add them to servers
(
guilds.join), so the app adds them to your server itself, with the role, within seconds. This is the door the portal's Connect Discord opens, and the reason the readiness checklist counts how many members have connected. - Neither — the app mints a single-use invite, valid for a week, into the server's system
channel (or the first text channel it can see) and hands it to the member: on the portal as
Join the server for …, in a direct message when the app can reach them, and in
/subscriby status. The moment the member joins through it, the app gives the role and the invite is spent. A purchase of two places needs one join. - No Discord account linked at all — the purchase waits as a pending grant until the member connects a Discord account on the portal; the portal says so, and the grant completes the moment they do.
After a grant the app sends the member one direct message listing what they now hold, with Join buttons for any invite still waiting and an Open button for the server. A member whose direct messages are closed to the app simply does not receive it; their access is not affected.
Ask members to connect Discord
A member who connected their account on the portal is added by the app itself, re-added by a failover without clicking anything, and written to Discord's Linked Roles. Everyone else depends on an invite they have to click. The Connect Discord for Every Member line on the readiness checklist shows the ratio.
Removing members
When access ends, whether by expiry, cancellation, a failed renewal after the grace window, a refund or a ban:
- Role — the role is taken back the same minute. A renewal brings it back.
- Channel — the role the app made for the channel is taken back, so the channel disappears for the member.
- Server — what you chose under When server access ends: by default the member keeps their seat and loses the roles their plan gave (each of those roles is its own grant and goes on its own), or the member is removed from the server. A removal waits while the member still holds another live place on the same server, so a server plan ending never throws out someone who keeps paying for a role or a channel there.
- An invite never used — withdrawn on Discord, so a lapsed member cannot join later with a stale link.
Discord's own bans stay yours: the app never bans anyone, and a member you ban in Subscriby loses their roles (and their seat, when a server plan says so) through the same removal.
Keeping the server in step
Every fifteen minutes the ledger is compared with the server: a member with live access who is missing a role gets it back, a member whose access ended and still carries one loses it. The reconciliation only ever touches members who are in the server and never removes anyone from it; removal is the explicit act of a server plan ending. This is also what covers the rare event the live connection missed.
The hourly probe, and Run Doctor on demand, checks the places themselves: a role deleted on Discord shows as gone, a role dragged above the app's as drag the Subscriby role above …, a channel the app can no longer see as check its permissions. A renamed role or channel is still the same place; Discord ids never change.
Passes and windows
A pass or a pass series grants its place at the window's start, not before: on Discord a role is
given in an instant, so there is no queue to hold a member in. Holders see the window on the server's
event calendar when Pass windows as events applies to the place, and
/subscriby passes lists what they hold.
Linked Roles
Beyond the roles a plan grants, Discord's own Linked Roles let any role require a verified Subscriby membership: whether the member is active, how long they have been one, how many plans they hold. The app writes those three facts per member from the ledger. See Linked Roles.
What the app does not do
- It never manages a role above its own in the role list, which is why the drag step matters.
- It reads messages in three places only: channels you mirror into a standby, the support threads it opened, and direct messages people send it.
- It cannot message a member who closed direct messages to it; their invite still waits on the
portal and in
/subscriby status. - It has no payment of its own: every purchase goes through your gateways on the portal.
- It holds nobody at a door before a window opens; the role arrives at the start of the window.
Related
- What the app can do — every command and message, for members and for you.
- Running your server — the members area, broadcasts, support and alerts.
- Resources — the connector-neutral picture of places and plans.
- Disaster Recovery — standby places, the live mirror and failover.
How is this guide?
Last updated on
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.
What the App Can Do
Every feature the app exposes to members and to you: slash commands in the server, the welcome message, broadcasts in a channel, support threads, alerts, the Copilot and the automatic role management behind it all.