Configure sheet mappings in SheetWeb

The SheetWeb sheet mappings editor gives mana/moni one place to manage the ranges TiaraBot reads from a Google Sheet. It keeps the current source running while you prepare a replacement, so changing a mapping does not change a live tiering shift by accident.

Open the editor

Go to Dashboard → [your server] → Server settings → Sheet mappings. The editor is organized into Overview, Users, Teams, Schedules, and Runners.

If the sheet cannot be read, check that TiaraBot's configured reader can access the spreadsheet and that the expected tabs still exist. Use Retry after correcting access.

Import an existing setup

Servers that already use TiaraBot's legacy Thee's Sheet Settings tab should start from the Overview section.

1. Select Import to draft.
2. Inspect the imported fields and the source status.
3. Fix any items under Needs review.
4. Edit the mappings, save the draft, and review the activation diff.

The import never writes to or modifies the spreadsheet. It copies the legacy settings into an editable draft and records the legacy layout and values as a baseline. The legacy source stays live and untouched until you activate a web revision.

If the legacy tab has moved, been renamed ambiguously, or no longer matches its expected layout, the import can finish with diagnostics instead of a usable configuration. Resolve those diagnostics in the editor or restore the legacy layout before trying again.

Establish the schedule time reference

Schedule Hour is an event-wide, one-based value. A full-event reference starts at Schedule Hour 1. An existing chapter can use a chapter-start reference instead, paired with the chapter's first event-wide hour—for example, a chapter starting at hour 49 keeps hour 49 at its configured start time.

When SheetWeb finds an older configuration without an established reference, the review flow shows the workspace-wide compatibility mapping before it is applied. Review the proposed reference and its hour/time examples, then establish it from the Sheet mappings editor. The mapping is validated against the active source and remains stable when schedule rows or visibility change; it is never re-based on the first visible row.

For a server without an existing legacy setup, enter a Google spreadsheet ID in Overview and choose Create draft. You can then map its tabs and ranges.

Export or import a configuration file

Use Move a configuration on the Overview section to move a complete web configuration between servers or keep a backup of the current draft or active owned configuration.

1. Choose Export JSON to download the configuration shown in the editor. Unsaved browser edits are included in the file.
2. Choose Choose JSON file and select a file exported by SheetWeb or TiaraBot.
3. Review the file contents and field-change count.
4. Choose IMPORT TO DRAFT only when the preview is correct.

The file uses the tiarastack.sheet-configuration format at version 1. It contains the spreadsheet ID, ranges, teams, schedules, runners, and event time. It does not contain a workspace ID, revision ID, or audit data, so the same file can be used in another server. Files larger than 1 MiB and files with schema or validation errors are rejected before anything is saved.

An import replaces the saved draft after confirmation. It does not activate the configuration, alter the Google Sheet, or change the source TiaraBot currently uses. Save and review the activation diff when the imported draft is ready to become live.

Work in a draft

The editor follows this lifecycle:

Use Save draft as you work. Saving does not activate anything. When the draft is ready, choose Review activation to see the field-by-field changes grouped by Users, Teams, Schedules, and Runners. Activation selects the existing immutable revision identified by SheetConfigurationActivateInput.revisionId, makes it active, and records who activated it.

Errors stay attached to the draft and block revision creation or activation until you fix them. Warnings remain visible for review. If you leave with unsaved changes or an incomplete range edit, the editor asks before discarding them.

Map ranges like a sheet formula

Open a mapping under Users, Teams, or Schedules to see its current A1 address, expected cell shape, and a read-only preview of the sheet.

You can set a range in either of two ways:

• Type a tab-qualified A1 address, such as 'Schedule Tab'!D3:F5.
• Click or drag across the preview grid, then choose Apply to draft.

The grid selection is staged first. It does not change the draft until you apply it, and applying it does not save the draft until you choose Save draft. Use View options to inspect nearby rows and columns without changing the mapping. The preview is read-only and shows only the visible window.

Runners use hour intervals instead of sheet ranges. Edit them in the Runners section with values such as 8-10, 12-14.

Review before activation

The activation review shows:

• the source that is currently live and the web revision that will replace it;
• every changed field, including its previous and new value;
• a fresh read-only sample for each changed mapping when the sheet can be read; and
• any diagnostics that must be fixed first.

The samples are a quick check of the changed mappings, not a full validation of every cell in the spreadsheet. If a sample is unavailable, verify sharing and tab access, then retry before relying on the preview.

After activation, the web revision becomes authoritative for sheet-backed operations. The imported legacy source is retained so you can choose Restore legacy source from the activation history if you need to return to it. Earlier web revisions remain available through Roll back.

Discarding a draft also leaves the active source alone.

Related TiaraBot controls

TiaraBot's Discord /sheet commands provide an alternate way to manage an owned web configuration. Use /sheet export to receive the current draft or active owned configuration as a JSON attachment. Use /sheet import with the attachment and confirm:false to preview it. Run the command again with confirm:true to save it as the draft. The bot checks the same file format and keeps the active source unchanged. Legacy-active servers must use the browser editor to import the legacy Settings tab before using the bot transfer commands.

The TiaraBot command reference lists the parameters and the update-announcement guide explains how bot-delivered product updates are handled.