Release 2026.18.1 continues reserved seat stabilization in Go Method, with corrections to assigning seats on trips that aren't shown on the public listing, who can grant, transfer, and release reserved seats, and merging duplicate profiles.

For more detailed help, see Reserved Seats.

Reserved Seat and Profile Merge Corrections

Issue	What was corrected
Seat owners couldn't assign seats on a trip that wasn't shown on the public listing	When a seat owner opened their reserved seats for a trip that had Show on public listing turned off and selected Assign, they saw the message "Something went wrong while loading the reserved seats for this trip" and couldn't go any further. Seat owners can now reserve and assign seats on a trip whether or not it appears on the public listing.
Trip administrators without full trip permissions could manage reserved seats	A trip administrator whose permissions for a trip didn't include managing trip information could still grant, transfer, and release that trip's reserved seats if they also held any global administrator role, however limited. Granting, transferring, and releasing reserved seats now follows the administrator's permissions for that specific trip.
Administrators received an error when merging duplicate profiles	When an administrator merged two profiles, the merge could stop with an error instead of finishing, most often when the duplicate profile had a sign-in, had answered application questions, or was linked to a guardian. A merge that did finish could also leave some of the duplicate's information behind, including trip participation, background checks, and emergency contacts. Merging now completes for these profiles, moves the duplicate's information to the profile you keep, and reports an error rather than success if any part of the merge doesn't finish.