Platform Updates

Repository: Partners. Status: Source updated; local typecheck, build, and browser fixture passed. Hosted rollout is pending the Git-linked build.

What’s Changed

Each attendee registration now has a paperclip attachment icon alongside the other EMS roster actions. Organizers can drag files into the attachment dialog or choose several files at once. JPEG, PNG, and PDF files remain limited to 10 MB each.

Impact

Organizers can open attachments without going through registration details. Successfully uploaded files appear in the attendee’s transaction details.

Upgrade Notes

Use the paperclip action on an attendee’s roster row. The local browser fixture confirmed a PDF drop and the resulting file list; it does not confirm a live storage upload.

Repository: Partners API. Status: Hosted storage configuration updated; authenticated upload confirmation pending.

What’s Changed

The API now has the protected file-storage configuration required for organizer attachments. Upload errors distinguish a storage outage from a registration-record failure so operators can resolve future interruptions faster.

Impact

Organizers can retry JPEG, PNG, and PDF attachments of up to 10 MB from an attendee’s EMS rego. Files remain encrypted in managed Sanity storage and visible only through the registration access checks.

Upgrade Notes

Retry a previously failed upload. The hosted configuration is present and local API checks passed; a signed-in live upload has not yet been confirmed.

Repositories: Partners, Partners API, and Docs. Status: Source and database migration published; Cloudflare builds and local checks passed. A real staff bot receipt remains unverified.

What’s Changed

EPS now treats a staff member’s verified private Telegram and Discord bot chats as required delivery routes for their own assignments, submissions, workflow changes, and deadline reminders. These messages follow the mandatory email schedule. Existing shared Telegram and Discord bot channels remain available for team updates, and SMS retains its separate consent controls.

Impact

The EPS Notifications page shows each private chat’s readiness and keeps shared bot routes separate. Email continues when a private chat is unavailable; operators can use delivery history to identify bot failures.

Staff can now link or verify their personal bots and use Test DM directly from the event plan’s Notifications page. A linked social account awaiting private-chat verification shows that distinction, and its Test DM button explains why it is unavailable until verification succeeds. Partner-admin configuration controls stay restricted.

Private chat readiness now requires a successful test message from each bot. A linked account or an opened Discord DM channel alone does not prove the bot can reach that staff member. Earlier links without a confirmed message after verification return to pending for a fresh check.

Personal bot messages and Test DM now follow the established EMS notification layout: a clear category, headline, summary, event plan, relevant details, and next step. Discord presents these in an embed; Telegram uses formatted text. Confidential planning details still receive a generic private notice.

Discord personal messages now keep those details in one compact block like Telegram, and both bots escape staff-authored Markdown so names and planning text display as written. The message’s own labels remain formatted for quick reading.

If a previously verified private chat changes or loses permission, the EPS page now refreshes its status after a failed Test DM and guides staff to verify it again. The readiness badge and Test DM use the same current destination checks, so a stale green badge should no longer persist after a rejected test.

Telegram private-chat activation now escapes the bot message’s final punctuation correctly. Staff whose activation showed a Telegram provider error should choose Open bot to allow DMs again and send /start from the new link, then use Verify private chat and Test DM.

Personal Discord and Telegram bot messages now include an Open EPS button when the notification has a verified Partners dashboard link. The same button appears in a test message for an event plan. Staff can use it to return directly to EPS; messages without a valid EPS link omit it.

Only the owning partner’s administrators may now change notification preferences or manage shared reminder policies and destinations. Other staff can still view their channel readiness and link or verify their own private bot chats.

Upgrade Notes

Staff should link and verify both private bot chats from the event plan’s Notifications page or Account Settings, then use Test DM. Telegram requires staff to open the bot and send /start; Discord requires the bot to be allowed to DM the staff member in a shared server. Local browser, API, and schema checks cannot confirm a hosted bot message reached a staff member.

Repositories: Partners and Partners API. Status: Local validation passed; hosted sample delivery pending.

What’s Changed

Event operators now choose private Discord text channels from servers linked to their organization on the EMS notification page. The existing Discord bot sends event alerts and samples to those channels. The API checks that each channel belongs to a linked server and denies access to @everyone. Telegram staff-group delivery remains event-specific.

Impact

Saved event Discord webhooks no longer send EMS alerts. Existing event alert settings and Telegram groups remain available, but a Discord bot channel must be selected to resume Discord delivery. Partner-level Discord webhooks used for separate partner messages are unaffected.

Upgrade Notes

Enable event notifications, connect a Discord server with the bot installed, select a private staff channel, save, and send a sample. Give the bot access to view the channel, send messages, and embed links. Local checks do not prove a hosted staff channel received the sample.

Repositories: Partners and Partners API. Status: Local validation passed; hosted delivery check pending.

What’s Changed

Telegram and Discord event alerts now lead with the alert category and whether staff review is needed, followed by the update, event and organizer, relevant details, and a next step. Context and detail labels use colons; names, usernames, and record text are escaped where Markdown could change their meaning. Telegram uses MarkdownV2 and Discord uses an embed with Markdown where supported. Sample deliveries exercise bold, italic, underline, strikethrough, spoiler, code, quotes, and a link so staff can check rendering in the destination chat. Operator decisions show the acting person’s display name and username when available. Automatic rego confirmations identify the system and the saved confirmation policy or the no-payment reason. Dealers Den application alerts identify when the system marked a fee paid because no fee was due. The EMS notification page explains that operators must enable notifications before editing destinations or alert types.

Impact

Staff can identify which event an alert concerns, who made a decision, and what to review without relying on an internal event ID. Dealers Den application decisions and dealer registration status changes can now be selected as alert types. Notification destinations remain specific to each event and Telegram alerts go only to a configured private staff group.

Upgrade Notes

Enable notifications, select a private staff Telegram group or Discord bot channel, choose alert types, save, and send a sample. A passing local format check does not confirm receipt in a hosted chat.

Repositories: Partners and Partners API. Status: Source published; hosted Telegram delivery verification pending.

What’s Changed

Event operators can link a private staff Telegram group from the EMS notification configuration page and select it for that event’s alerts. Public and attendee entitlement chats are excluded from notification choices. The API checks the selected group’s privacy and access when settings are saved or a sample is sent.

Impact

EMS alerts for an event use its selected staff group, independently of the public event chat. Existing notification destinations that overlap attendee chats need to be removed and replaced with a private staff group.

Upgrade Notes

Connect a Telegram account if needed, add the bot to a staff-only private group, select the group on the event notification page, and save. If a group link reports an identity mismatch, use Verify Telegram account again on that page and start a new group link. Existing links may need this once because the previous OAuth flow saved a different Telegram ID claim. Send a sample to confirm delivery. Source publication does not establish that a specific staff group has been configured or received a hosted notification.

Repositories: Partners, Partners API, and Rego. Status: Source published; database and API release pending.

What’s Changed

Organizers can add a JPEG, PNG, or PDF file of up to 10 MB to an attendee registration from the EMS Attendee Rego screen. Attendees can find files shared with their registration in Transaction Details, above Onsite purchases.

Impact

Files belong to the specific attendee registration. Organizers manage them in EMS, and the attendee opens them from their own Rego transaction.

Upgrade Notes

The Supabase migration and API must be released before hosted uploads and downloads work. Hosted availability has not been verified.

Repositories: Rego and Partners. Status: Source published; hosted verification pending.

What’s Changed

Inclusion detail popups group the artwork, name, and description together. Item facts and included guidance follow in a compact, consistent layout on narrow and wide screens.

Impact

Attendees can find the item’s description and inclusion guidance without scanning across separate oversized panels. The same layout is used in Rego and the Partners registration preview.

Upgrade Notes

No action is needed. The updated layout has not yet been verified on hosted sites.

Repositories: Partners, Partners API, and Rego. Status: Local verification passed; hosted release pending.

What’s Changed

New individual, group, and imported staff walk-in registrations now use the event’s saved confirmation setting. Good faith confirms at submission. Hybrid confirms free registrations immediately and sends paid registrations with a payment method, reference, and receipt to review. Incomplete paid claims stay pending. Manual review also keeps complete paid claims in review. Gift purchases retain their existing confirmation policy. Events without a saved setting now display the actual manual-review default in the dashboard. When event payments are turned off, saved catalog prices remain available for later, while current quotes and registrations have no amount due. The attendee confirmation page now says “Rego confirmed” for accepted records with a confirmation time, including pay-on-site registrations. Incomplete paid records are labeled “Payment pending”.

Impact

Attendees and event operators see the correct status in registration receipts and the registration list. Confirmation time is recorded when a registration confirms immediately. Existing registrations are unchanged.

Upgrade Notes

The confirmation policy cases, fourteen disposable local API/database submissions covering individual, group, and imported walk-in registrations, and the API, Partners, and Rego type checks passed locally. The Rego build and controlled desktop/mobile confirmation receipts also passed. Payment links currently issue references without verifying settlement, so paid hybrid registrations still require review. A hosted end-to-end registration check remains necessary after release.

Repository: Rego. Status: Deployed display checks passed; live variation checkout pending.

What’s Changed

The deployed attendee site displays alternative designs, bundled items, and random-design promises in event, gift, and Dealers Den previews. Desktop and mobile checks used temporary browser-only sample event data; they did not create an event or registration.

Impact

Attendees can see the intended composition in these previews when an organizer configures variations. The checks do not establish that a real event currently offers one or that inventory allocation and collection work on the hosted system.

Upgrade Notes

No operator action is needed for the display check. A real hosted variation checkout and collection claim still require a configured event and separate verification.