Linked Roles
Put a verified-membership requirement on any Discord role: active member, member for at least so many days, so many live plans, written by the app from the membership ledger.
Discord's Linked Roles let a role carry a requirement that a connected app answers per member, the way a role can require a connected YouTube channel or a verified age. Subscriby answers three facts about a member, written from the membership ledger, so any role in your server can require a verified Subscriby membership on top of, or instead of, the roles the app gives directly.
The three requirements
| Requirement in Discord | True when |
|---|---|
| Active member | The member holds live access through Subscriby right now. |
| Member for at least (days) | Their first access through Subscriby started at least that many days ago. |
| Live plans (at least) | They hold live access on at least that many plans. |
A role can combine them: active member for at least 90 days, for example, with no role to give by hand.
A badge, not a plan gate
Discord keeps one record per member per app, the same in every server the member is in. The three facts count every Subscriby membership the member holds through Discord, so a Linked Role is a verified Subscriby member requirement. To gate a role on one plan, sell the role itself: the app gives and takes that role directly.
Setting a requirement on a role
In your server, open Server Settings → Roles and pick the role (or create one).
Open the role's Links tab and press Add requirement. Pick Subscriby from the connected apps, then the requirement and its value.
Save. The role now shows as a linked role in the server, and members claim it themselves.
How a member qualifies
The member clicks the linked role in your server (the Linked Roles entry in the server menu, or the role's name) and chooses Subscriby.
Discord sends them to Subscriby's verification page, which asks them to authorise the app, the same authorisation as Connect Discord on the portal.
The page confirms: Your Discord account is verified with Subscriby as …; head back to Discord: the linked roles you qualify for are yours now. Discord reads the record and gives the role when the requirement is met.
A member who connected Discord on the portal before is already written; the verification step only matters for members who never did.
When the record is written
The app writes a member's record:
- after every grant it completes, every removal, and every join through an invite;
- at the moment of verification;
- and keeps the member's authorisation renewed daily, so the record can be written months later.
Only members who authorised the app (through the portal's Connect Discord, through Continue with Discord on the portal, or through the verification page) can be written: Discord accepts a record only with the member's own authorisation. Everyone else is simply never written, and never qualifies, until they connect.
What it is good for
- A verified-member role that unlocks a lounge, a badge or an emoji set across every plan, claimed by members themselves, with no list to maintain.
- Tenure: a role for members of a year's standing, with Discord checking the date.
- Breadth: a role for members on two plans or more.
Related
- Integration — the roles the app gives directly, per plan.
- Joining through Discord — the member's side.
How is this guide?
Last updated on
Joining Through Discord
For members: buy on the portal, connect your Discord account, get your roles the moment you pay, and manage your membership with /subscriby without leaving Discord.
Pass Windows as Events
A window of access on a place becomes a Discord scheduled event, kept in step with the window: the server default, each place's own choice, the 30-day horizon and the events you made yourself.