Bug fix·2026.09.22·2026-09-23

Attendance correction and venue-specific booking access

Attendance corrections now enforce the operator's no-show/removal grants and class-location access. Assigned and substitute instructors retain their scoped permissions. An operator denied an organization-wide action cannot bypass that denial through an unrelated check-in grant.

# Attendance correction and venue-specific booking access

Attendance corrections now enforce the operator's no-show/removal grants and
class-location access. Assigned and substitute instructors retain their scoped
permissions. An operator denied an organization-wide action cannot bypass that
denial through an unrelated check-in grant.

Client messages require explicit Email, SMS or Push selection, send permission,
and usable channels. Leaving channels empty stays silent. Pending or held
notification effects are shown separately from a completed correction.

Corrections use the reviewed booking version and a stable operation key. Late
check-in permission is checked on the server, and ended classes require explicit
confirmation. Historical changes and refunds keep their protected workflows.

Venue-specific booking detail, cancellation and self-check-in remain inside the
venue supplied with the request. Consumer requests without a venue header retain
access to the signed-in client's bookings across venues. A stale self-check-in
asks the client to refresh instead of overwriting a newer cancellation.

An explicit user permission denial now also takes priority over own-class attendance permissions. Instructors keep their normal assigned-class access when no user denial is configured.

Next update

Unused-class leftover rules in Advanced pass settings

When unused classes roll into the next period, studios can cap leftover, carry through a pause, tell clients leftover is lost on termination, and roll class-pack leftover into the next pack bought before expiry.

# Attendance correction and venue-specific booking access Attendance corrections now enforce the operator's no-show/removal grants and class-location access. Assigned and substitute instructors retain their scoped permissions. An operator denied an organization-wide action cannot bypass that denial through an unrelated check-in grant. Client messages require explicit Email, SMS or Push selection, send permission, and usable channels. Leaving channels empty stays silent. Pending or held notification effects are shown separately from a completed correction. Corrections use the reviewed booking version and a stable operation key. Late check-in permission is checked on the server, and ended classes require explicit confirmation. Historical changes and refunds keep their protected workflows. Venue-specific booking detail, cancellation and self-check-in remain inside the venue supplied with the request. Consumer requests without a venue header retain access to the signed-in client's bookings across venues. A stale self-check-in asks the client to refresh instead of overwriting a newer cancellation. An explicit user permission denial now also takes priority over own-class attendance permissions. Instructors keep their normal assigned-class access when no user denial is configured.

All updates

Bug fix·2026.09.22·2026-09-23

Attendance correction and venue-specific booking access

# Attendance correction and venue-specific booking access

Attendance corrections now enforce the operator's no-show/removal grants and
class-location access. Assigned and substitute instructors retain their scoped
permissions. An operator denied an organization-wide action cannot bypass that
denial through an unrelated check-in grant.

Client messages require explicit Email, SMS or Push selection, send permission,
and usable channels. Leaving channels empty stays silent. Pending or held
notification effects are shown separately from a completed correction.

Corrections use the reviewed booking version and a stable operation key. Late
check-in permission is checked on the server, and ended classes require explicit
confirmation. Historical changes and refunds keep their protected workflows.

Venue-specific booking detail, cancellation and self-check-in remain inside the
venue supplied with the request. Consumer requests without a venue header retain
access to the signed-in client's bookings across venues. A stale self-check-in
asks the client to refresh instead of overwriting a newer cancellation.

An explicit user permission denial now also takes priority over own-class attendance permissions. Instructors keep their normal assigned-class access when no user denial is configured.

Next update