Skip to content

Connect tokens and service accounts

For super admins - connect tokens that let apps register themselves, the watch tower token, and service accounts for app-to-app calls and agents.

Connect tokens

"An app given REM Auth's address and one of these registers itself at deploy: its OIDC client, callbacks, brand and teams. Shown once."

  1. Open Connect tokens and create one. Give it a name ("rch deploys"), the product slugs it may register (*, rch-*, payments) and an expiry if you want one (empty: never).

  2. Copy the token (rat_...); it is shown once and stored only as a hash.

  3. Put it in the app's deployment secrets as REMAUTH_REGISTRATION_TOKEN, next to REMAUTH_URL=https://auth.remplatforms.com.

Revoking a token: "Deploys using it can no longer register or update their product. Products already registered keep working." To rotate, revoke and make a new one.

A connect token can also be made for the watch tower (rpt_...): it can only read sign-in counts for REM's internal admin, nothing else.

Service accounts

"Accounts for apps and agents, not people: app-to-app calls, MCP, scripts. A token acts with exactly its account's permissions."

  1. Open Service accounts and add one. Put it in teams to give it what those teams may do.

  2. Make an API token for it. Expiring tokens are rotated; turn expiry off only for long-lived integrations.

  3. Hand the token over once. All tokens (advanced) lists every token; "View a key only when you need to hand it over."

Delete a token under All tokens to stop it; make the new one first.

Last updated 18 Nov 2026

Connect tokens and service accounts · REM Platforms Blog