Access & Migration

Only administrators can manage the permitted Discord account list or import the previous JSONBin records. Do not share the old JSONBin master key; it is used only for the one-time import form and is not saved by this page.

1. Add an approved Discord account

Use the account's numeric Discord user ID, not a username. The member does not need to configure cloud sync after being allowlisted.

Discord user IDRoster match name (optional)

Pantheon normally matches a Discord profile name to the same-named Member Roster owner automatically. Use Roster match name only if those names differ; enter the exact owner name once. To copy a Discord ID, enable User Settings → Advanced → Developer Mode, then right-click the user's profile and choose Copy User ID.

2. Move the old guild record from JSONBin to D1

Run this once, from an administrator session, to copy the existing tracker and revision journal into Cloudflare D1. The target records are the private IDs used by the new Pantheon backend. This leaves the old JSONBin records untouched as a backup.

Existing main JSONBin IDExisting JSONBin Master Key

I understand this imports the selected main record into Pantheon D1 and overwrites the new Pantheon main record if it already exists.

3. Initialize an empty database instead

Use this only if there is no JSONBin data to migrate. It creates a clean, empty tracker record. It will not overwrite an existing main record.