Small changes. Better testing.

New team members signing in through Microsoft SSO could hit an "Invalid invitation" error when opening their invite link.

• Fixed invitation acceptance for users whose identity provider does not report a verified email
• Improved invitation error pages to show the actual reason instead of a generic message

Teams are now called Access Groups and available to every organization, no add-on required.

• Renamed Teams to Access Groups across the dashboard, docs, and pricing
• Removed the add-on requirement so any organization can scope station and member access
• Updated documentation with the new Access Groups guide

Self-hosted instances take a database snapshot before applying upgrade migrations, but a version mismatch had silently prevented it from completing, and snapshots were not kept across upgrades.

• Fixed the pre-upgrade database backup so it completes and persists in a dedicated storage volume across upgrades
• Added clear log output when a backup fails, with an optional strict mode (REQUIRE_BACKUP) that halts the upgrade instead of continuing without one
• Limited backups to one per version with automatic cleanup so they never fill the server disk

A recent security upgrade hardened how sign-ins from identity providers attach to existing accounts, which could lock out a small set of long-standing accounts on upgraded self-hosted instances.

Self-hosted instances migrating to the new deployment architecture now get a smoother, more reliable experience, even on restricted networks.

• Improved resilience when optional deployment services are not yet configured, removing recurring errors from instance logs.
• Added a prebuilt build environment so new deployments start faster without downloading dependencies at boot.
• Fixed sign-in for existing members using single sign-on after upgrading from older versions.

User seat limits are now enforced server-side on self-hosted instances, so member management respects your license.

• Enforced the user cap on invitations, matching how station limits already work.
• Kept re-invites and role changes unaffected, since they add no seat.

New users signing in through Microsoft or Azure AD SSO could fail to be created when their account had a profile photo, because Microsoft sends the photo as inline image data that exceeded an internal limit on the avatar field.

• Fixed account creation for Microsoft and Azure AD SSO users who have a profile photo
• Improved handling of inline profile photos so they no longer block sign-up
• Added a fallback to initials when no uploaded avatar is set

Code examples now use an obviously-fake placeholder procedure ID instead of a name or a real-looking UUID, so a copy-pasted snippet can't accidentally target a real procedure and clearly reads as a value to replace.

• Replaced name-style (FVT1) and a real-looking UUID with xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx across the OpenHTF and SDK docs and the V1 API example.
• Clarified that procedure_id is the dashboard procedure UUID (a legacy external identifier only resolves if one was set).
• Updated the OpenHTF client docstrings and released python client 2.13.2.

Switching between organizations is now easier, and invitations you haven't accepted yet show up where you'd expect them.

• Added pending invitations to the organization switcher, so you can accept an invite without hunting for the email
• Improved the expired-demo experience with a dedicated screen that keeps the switcher available so you can move to your other workspaces

You can now invite teammates to your organization directly from connected MCP, and invites can no longer grant a role above your own.

• Added a tool to invite members by email from connected AI assistants, with the invite sent automatically.
• Prevented inviting or promoting someone to a role higher than yours, closing a privilege-escalation gap across the dashboard and API.
• Filtered the invite role picker to the roles you're allowed to grant.