RG
RG Herd
Help Center

Practical onboarding • No platform mysticism • Save your keys

Help Center

This page is a living guide for joining | base | and operating safely on a Matrix-based network using Element clients (Element X on mobile, Element Web on desktop).

Getting Started

Matrix works a bit like email for chat. You choose a homeserver (like choosing an email provider), then use a client app to connect to it. Your account lives on the homeserver. The app is just how you access it.

For RG Herd, | base | runs on the homeserver rgherd.com. When you create an account there, you’re joining the network directly — not a corporate platform layered in between.

Registration is intentionally structured. Instead of open sign-ups, new accounts are created using registration tokens. This keeps spam down, protects encrypted rooms, and preserves signal quality.

OVERVIEW
~2–3 minutes
  1. Obtain a registration token from a trusted member or Ops
  2. Open Element X (mobile) or Element Web (desktop)
  3. Select Create account
  4. Set the homeserver to rgherd.com
  5. Enter your token when prompted
  6. Set up Secure Backup and save your Recovery Key
  7. Verify your device
About Tokens

A registration token is a one-time or limited-use key that authorizes account creation. It does not give anyone access to your messages. It simply allows the server to accept your account request.

  • Tokens may expire or be single-use.
  • Homeserver must be set correctly to rgherd.com before registering.
  • Screens vary slightly between Element versions.
Heads-up (important)
  • If you lose your Recovery Key, you can lose access to encrypted history on new devices.
  • Verification matters: encryption depends on trusted sessions.
  • Encryption is per-room: some rooms are encrypted, some are not.

Recommended: store your Recovery Key in a password manager or secure offline location.

Common registration issues
  • Homeserver not set to rgherd.com
  • Token expired or already used
  • Client cached a previous login method

If something fails, it’s usually one of these. Ops can reissue tokens or walk you through it.

Registration

Public registration may be closed or wave-based. Most new users will join via a token from a trusted member or direct Ops onboarding.

Token onboarding

Create Account with a Token

  1. Open your client (Element X or Element Web)
  2. Choose Create account
  3. Edit/select homeserver and set it to: rgherd.com
  4. Continue and follow prompts (the server will present available registration methods)
  5. When prompted, enter your registration token

Note: the exact screens vary by client/version. The homeserver step is the one people commonly miss.

Ops onboarding

If you’re stuck

If registration fails, you’re probably hitting one of these:

  • Homeserver not set to rgherd.com
  • Token expired / already used
  • Wave closed
  • Client cached an old login method

Choose Your Client

You can access the same Matrix account from multiple clients. Most people use Element X on mobile and Element Web on desktop.

Mobile

Element X

Best for day-to-day messaging and field use. Expect the app to strongly push device verification and recovery setup.

Common flow
Create account → Edit homeserver → rgherd.com → Register/Login → Verify device → Set up Secure Backup

Tip: if you have a Recovery Key from an existing session, keep it ready when adding a new device.

Desktop

Element Web

Best for admin tasks, longer writing, and multi-room workflows. If you’ve used Slack/Discord on desktop, this will feel familiar — except encryption makes it more serious.

Common gotcha
People accidentally create accounts on the matrix.org homeserver. Always click Edit and set it to base.rgherd.com on desktop.

Element Web is also where many encryption/backup settings are easiest to find.

Encryption Basics

Matrix supports end-to-end encryption (E2EE). In encrypted rooms, the server can’t read your message contents. That’s the point — but it means you must take key backup seriously.

The single most important onboarding action: set up Secure Backup and save your Recovery Key. Without it, adding a new device can be painful, and you may lose access to older encrypted history on that new device.

Official User Guide:

Secure Backup checklist
  1. Open Settings
  2. Find Security & Privacy (or Encryption)
  3. Look for Secure Backup / Key Backup
  4. Choose a Recovery method (security key or phrase, depending on client)
  5. Save it offline (password manager or printed copy)

Recovery Key = access to your encrypted key backup. Treat it like “the keys to the keys.”

Device and User Verification

Verification links your sessions/devices together so encryption works cleanly across them. In practice, this reduces impersonation risk and prevents weird “I can’t decrypt” moments on new devices.

What you’ll see

“Verify this device” prompts

When you sign in on a new device, Element will typically prompt you to verify it using one of:

  • Approve from an already-verified device
  • Enter your Recovery Key / Security Key
  • Scan a QR code (in some flows)

The wording varies by client version. The underlying idea is always the same: prove this new session is really you.

Why it matters

Unverified devices become dead weight

The Matrix/Element ecosystem is trending toward verified-only participation for end-to-end encrypted rooms. If you don’t verify, you can end up unable to send/receive E2EE messages properly.

Official reference: Verifying your devices is becoming mandatory (Element blog)

Also important

Verifying other users (identity check)

Device verification proves a new login is you. User verification is different: it proves you’re talking to the real encryption identity for that account (not a hijacked session or an impersonator on a lookalike account).

  • When a user is verified, Element treats their cross-signed devices as trusted (so you don’t have to “trust every device” forever).
  • Verification is about keys, not real-world identity. It doesn’t tell you who they are offline.
  • Verification reduces man-in-the-middle risk and makes E2EE warnings meaningful instead of constant noise.

Plain English: you’re confirming “this is the correct encrypted identity for @thatperson,” not “I like/trust everything they say.”

How it works in Element

Emoji / numbers match, or QR scan

In Element clients, user verification usually happens like this:

  1. Open a DM or room with the person
  2. Click/tap their name (profile)
  3. Open Security (or “Encryption” / “Verification” depending on client)
  4. Choose Verify
  5. Complete one method:
    • Match emoji / numbers on a voice call or in person
    • Scan a QR code if the client offers it

Best practice: do the match out-of-band (voice call / in person), not by pasting the emojis back into the same chat you’re trying to secure.

Troubleshooting

This section is intentionally short right now. It’ll grow as we see real-world user issues.

I can’t register

  • Confirm homeserver is set to rgherd.com
  • Confirm token is valid (not expired / not reused)
  • If wave-based registration is closed, you’ll need Ops onboarding

I can’t decrypt messages on a new device

  • Verify the new device
  • Set up Secure Backup and restore keys using your Recovery Key
  • If you never saved a Recovery Key, older encrypted history may not be recoverable on that device

Contact Ops

Need onboarding help, a token, or a deployment consult? Email Ops.

Include: which client you’re using (Element X / Element Web), what step failed, and any on-screen error text.

Help page status

This help center is actively being built. The goal is to keep it short, clear, and field-usable — not a wiki nobody reads. Expect updates as onboarding expands.

Last note: if you’re new to Matrix, you’re not “behind.” This stuff is powerful because it’s not a single platform. That power comes with a couple responsibilities: save your Recovery Key and verify your devices.