Add fit guidance & alternatives to Publisher Level Account Linking docs#8267
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
anthonydiscord
left a comment
anthonydiscord
left a comment
There was a problem hiding this comment.
Only one wording callout, otherwise this looks solid!
| #### Authorization is all-or-nothing at the publisher level: | ||
| - When a player links their Discord account to the publisher application, that authorization applies to **all** child game applications under the publisher | ||
| - Players cannot opt out of the Discord connection for individual games while remaining linked at the publisher level | ||
| - Revoking authorization disconnects Discord from the publisher account entirely, affecting all games |
There was a problem hiding this comment.
Is there better wording from this? It sounds like this means if you deatuhorize in one game it deauthorizes in all of them with publisher level account linking (by nature of authorizing in one across all)
There was a problem hiding this comment.
It sounds like this means if you deatuhorize in one game it deauthorizes in all of them with publisher level account linking (by nature of authorizing in one across all)
That's 100% correct. If you disconnect your Discord account from any game from that publisher authentication - you are removed from the whole set. (You do get a provisional account though -- maybe that part should be clearer)
There was a problem hiding this comment.
Made a small tweak to the language, should be a bit nicer.
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.
markmandel
force-pushed
the
markm/publisher-auth-chat
branch
from
dd90f57 to
b5a6bc2
Compare
…cs (discord#8267) * 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. * Small tweak to language.
2 participants
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.