Docs / Alliance (cross-org)

Pairing with an ally

How to actually link two mustr instances: generate an invite, send the connect code, and the ally pastes it once.

Pairing lives under Admin → Settings → Alliance on both orgs' sites. Whoever initiates sends an invite; the other side redeems it. That's the whole process — no tokens are typed or swapped by hand.

Step 1 — Generate an invite

1

On your site, open Admin → Settings → Alliance.

2

Under Invite an ally, optionally type a label (e.g. the ally's name, just for your own reference), then click Generate invite.

3

A one-time connect code appears. Copy it and send it to whoever runs the allied org's mustr — Discord DM, email, whatever channel you'd trust with a password.

One-time and expiring

The code works once and expires after 7 days. If it's used or expires unredeemed, generate a fresh one — nothing about the old one still works.

Step 2 — The ally joins

1

On their site, they open Admin → Settings → Alliance.

2

Under Join an alliance, they paste the connect code and click Connect.

3

Both sites are now linked, two-way, automatically — no separate step on your end.

Step 3 — Pick a channel

Back on each side's Alliance panel, under Linked orgs, pick the Discord channel that ally's broadcasts should post into. Nothing arrives anywhere until a channel is chosen.

Step 4 — Verify it works

Click Send test broadcast. If everything's wired correctly, a test message shows up in the channel you picked on the other side within a few seconds.

Managing a link

Testing solo

You can pair an instance to itself to test the whole pipe without a second org: generate an invite, then paste that same connect code into your own "Join an alliance" box. A shared event or tournament will then round-trip back to your own Discord channel.

The advanced/manual flow

If the connect-code flow isn't an option for some reason, an "Add manually (advanced)" section on the same page still supports the older two-way token exchange: enter the ally's name and site URL, mint a token for them, and paste the token they mint for you. This is the same mechanism connect codes automate — kept as a fallback, not the recommended path.