Path 2 · Optional add-on

Add Communities

You are a developer who needs Matrix-backed community — rooms, spaces, and MXIDs — on top of Briij identity (and usually the same wallet login your users already have).

← All paths · New to Briij login/wallet? Start with Identity + Wallet, then return here.

The story

Your product is not only “sign in.” You want members to land in a community: DMs, rooms, spaces, bots — with identities that match their Briij login. Briij runs the homeserver OIDC bridge so a successful wallet/passkey login mints or resumes an MXID on matrix.briij.org.

Walkthrough

1. Have Identity + Wallet working first

   You need a Briij OIDC client and a working authorize → token path. If you do not, complete Path 1.

   Issuer:     https://auth.briij.org/
   Homeserver: https://matrix.briij.org
   MXID domain: matrix.briij.org

2. Enable the Communities add-on on your client

   Community login needs the matrix scope (and usually openid profile offline_access).

   Today: self-serve portal clients default to Identity + Wallet (identity product). Matrix scope is enabled by ops when you request Communities:

   • From the portal, create/keep your app, then contact ops with: partner name, client_id, redirect URIs, and “enable Communities / matrix scope”.
   • Or ops runs provision-partner.sh with community/matrix flags for a dedicated HS-facing client.

   First-party reference client on prod: briij-matrix-client-prod.

3. Start community login from the homeserver bridge

   Recommended browser entry (hosted path):

   https://matrix.briij.org/_briij/client/oidc/start?returnUrl=https://YOUR_APP/community/land

   What happens:

   1. Homeserver starts OIDC against auth.briij.org with wallet=1 and matrix scope.
   2. User completes passkey/wallet on Briij.
   3. HS finishes callback and establishes a Matrix session.
   4. Browser returns to your returnUrl.

4. Use Matrix as usual after session exists

   Point Matrix clients / your embedded client at:

   Homeserver base URL: https://matrix.briij.org

   User id form: @localpart:matrix.briij.org. Your app should treat Briij sub (from IdP tokens) and MXID as linked identifiers for the same person when both are present.

5. Scopes checklist

   Scope	Why
   openid	OIDC subject
   profile	Profile claims
   offline_access	Refresh / long sessions
   matrix	Community / MXID bridge (add-on)

6. Limits that matter for Communities

   Core auth caps still apply (MAU, RPM, daily). Communities adds tier fields for spaces and active MXIDs. Over commercial caps → 402; pure rate → 429. See limits.

Done when

• OIDC start URL sends you through Briij wallet/passkey and back to your returnUrl.
• You can call Matrix Client-Server APIs on matrix.briij.org as the logged-in MXID.
• The same human can also use pure Identity + Wallet login in your main app (shared Briij account).

Smoke URL (backend)

https://matrix.briij.org/_briij/client/oidc/start?returnUrl=https://matrix.briij.org/

Use this for a quick human check that Communities OIDC + wallet still completes end-to-end.