Skip to content

Commit dd90f57

Browse files
committed
Add fit guidance & alternatives to Publisher Level Account Linking docs
Adds an "Is This Right for You?" section covering good fit vs poor fit, key architectural constraints (all-or-nothing auth scope, publisher-level friend lists, one-way migration), and an alternatives section for publishers without a shared social graph.
1 parent 03cfb58 commit dd90f57

1 file changed

Lines changed: 43 additions & 0 deletions

File tree

developers/discord-social-sdk/development-guides/publisher-level-account-linking.mdx

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,36 @@ This guide will show you how to:
3838
- **Simplified Experience**: Reduced friction when playing multiple games from the same publisher
3939
- **Richer Social Features**: Access enriched friend data and activity across the publisher's game catalog
4040

41+
---
42+
43+
## Is Publisher Level Account Linking Right for You?
44+
45+
Publisher Level Account Linking is designed for publishers with centralized, cross-game social ecosystems. Not all multi-game publishers are a good fit.
46+
47+
| **Good Fit** | **Poor Fit** |
48+
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------|
49+
| Publishers with cohesive portfolios where games share a centralized account system **and** a publisher-level social experience (shared friends list across games). | Publishers with disparate game portfolios that share only a centralized login but have no cross-game social features. |
50+
51+
Publisher Level Account Linking was designed to support publishers with cross-game social ecosystems. When a player links their Discord account to a publisher account and that publisher shares a social graph across games, the authorization feels natural and expected — players already understand that their friends in one game appear across all games in the portfolio.
52+
53+
### Key Behaviors to Understand
54+
55+
Before committing to Publisher Level Account Linking, understand these architectural constraints:
56+
57+
#### Authorization is all-or-nothing at the publisher level:
58+
- When a player links their Discord account to the publisher application, that authorization applies to **all** child game applications under the publisher
59+
- Players cannot opt out of the Discord connection for individual games while remaining linked at the publisher level
60+
- Revoking authorization disconnects Discord from the publisher account entirely, affecting all games
61+
62+
#### Relationships exist at the publisher level, not per-game:
63+
64+
Game friend lists exist at the publisher level — there are no per-game sandboxed friend lists. If you need separate friend lists per game, Publisher Level Account Linking is not the right solution.
65+
66+
<Warning>
67+
**This is a one-way architectural decision.** Once child applications are linked to a parent publisher application, [data is deleted and the relationship cannot be reverted](#3-establish-parent-child-relationships). Evaluate carefully before migrating existing applications.
68+
</Warning>
69+
70+
4171
---
4272

4373
## How It Works
@@ -452,6 +482,19 @@ For more details on the token revocation API and additional options, see [Revoki
452482

453483
---
454484

485+
## Alternatives for Publishers Without a Shared Social Graph
486+
487+
488+
If your studio operates a centralized publisher account system but doesn't have a shared social graph across games, you can still build your own
489+
centralized backend system that manages per-game Discord application IDs with the standard authentication model. This lets you reuse Social SDK integration logic across titles while keeping each game's Discord connection separate.
490+
491+
There is also potential for you to build a publisher account settings UI that lets players link, unlink, and manage which Discord account is connected to each game, giving players finer-grained control over their account linking experience.
492+
493+
The trade-off is that players will need to authorize each game individually, and it requires more development, but it also provides players more control over which games they link to their Discord accounts – which may well make more
494+
sense for your individual studio or game specific needs.
495+
496+
---
497+
455498
## Next Steps
456499

457500
Now that you've set up publisher level account linking, explore more features of the Discord Social SDK:

0 commit comments

Comments
 (0)