February 10, 2026
2026.02 – Scheduling safeguards
Added overlap detection for location/role conflicts.
New delivery status for SMS/email reminders.
Improved audit entries for reschedules and cancellations.
Primary actions
Use these notes to guide your rollout
Pick a version, identify the roles affected, and communicate the steps.
January 23, 2026
2026.01 – Permissions refresh
Separated billing privileges from general admin.
Role changes now require confirmation and are logged.
Minor UI cleanup for settings navigation.
Current status / summary
What to know about the latest release
Area
Summary
Scheduling
Stronger conflict detection now live.
Notifications
Delivery tracking added for reminders.
Permissions
Billing privileges split from admin role.
After you read a release note
Assess impact
Identify which roles and locations are affected.
Plan rollout
Schedule changes during low-risk windows and inform staff.
Monitor signals
Watch status and KPIs tied to the change for 24–48 hours.
Recent activity / history
Date
Action
Owner
Feb 10, 2026
Release 2026.02 published with scheduling safeguards.
Product
Jan 23, 2026
Release 2026.01 permissions refresh shipped.
Engineering
Jan 12, 2026
Release communications template updated.
Support Ops
Operational depth
Convert releases into clear adoption and readiness guidance
Release notes should explain what changed, who is affected, and what validation steps teams should perform before broad rollout.
Primary audience
Rollout managers, admins, and support enablement teams
Decision focus
Approve release adoption timing based on impact scope and team readiness
Operational risk
Adopting updates without role-based readiness checks increases operational friction
Field scenario
A workspace prepares for an update window and needs a concrete validation checklist.
Execution walkthrough
1. Frame the objective
Release notes should explain what changed, who is affected, and what validation steps teams should perform before broad rollout.
2. Align participants
Rollout managers, admins, and support enablement teams
3. Validate the decision
Approve release adoption timing based on impact scope and team readiness
4. Mitigate known risk
Adopting updates without role-based readiness checks increases operational friction
Interpretation matrix
Signal
Interpretation
Operational scenario
A workspace prepares for an update window and needs a concrete validation checklist.
Successful outcome
Successful use of this page leaves teams with clear direction on Approve release adoption timing based on impact scope and team readiness.
If skipped
Skipping this step often introduces Adopting updates without role-based readiness checks increases operational friction.
Recommended next step
Use changelog for granular entries and support docs for procedural follow-through.