Firms standardized on Entra ID, Okta, or Google Workspace have had to manage a second set of Stax.ai credentials — separate passwords, separate off-boarding, and no way to apply their own access policies to the platform.

Stax.ai now supports SAML 2.0 single sign-on. An admin connects your identity provider once from your organization's settings, either by uploading its metadata file, pointing at a metadata URL, or entering the details by hand. From then on your team signs in through your provider, and the access rules you already enforce there apply to Stax.ai too. Both directions work: starting from Stax.ai, or launching Stax.ai from your provider's app portal.

By default, a person must already be invited to your organization before they can sign in through SSO, so no one arrives unexpectedly. If you'd rather have accounts created on first sign-in, that can be enabled for your organization. Password sign-in continues to work exactly as before for anyone not on SSO.

SSO is rolling out to organizations now — talk to your account manager to get it turned on and configured.

Automatic user provisioning and de-provisioning

Single sign-on controls how people sign in. Directory sync controls who exists in the first place.

Stax.ai now supports SCIM 2.0, so your identity provider can create, update, and deactivate Stax.ai users automatically. When someone joins, their account is created with the right details. When their role changes, it updates. When they leave your firm, their Stax.ai access is revoked with them — no ticket, no manual cleanup, no dormant accounts left open.

Groups sync as well, and map to Stax.ai groups so permissions follow directly from your directory. Groups that originate in your provider stay owned by your provider for naming and membership, while your Stax.ai admins keep control of the settings on them.

Setup uses a dedicated provisioning token generated from your integration settings, separate from anyone's login. Available alongside SSO — your account manager can enable both together.

Stop a bulk send before it goes out incomplete

Some mailings you can't afford to get partly right. Bulk email send settings now include a new option beneath the recipient fields: Stop the send if any recipient can't be evaluated.

Turn it on and Stax.ai builds every message before sending any of them. If even one recipient can't be resolved, nothing goes out, the full list of problem recipients is recorded for you to review, and you're notified. It's off by default, so existing and scheduled sends behave exactly as they do today.

Copy Variables automation now works with plan years

The Copy Variables automation can now use a plan year as its source or its destination, alongside the project types it already supported.

Pick Plan Year in the automation's source or destination configuration and Stax.ai will find the matching plan year project and copy the variable across. If you've set a plan year as the destination and that plan year project doesn't exist yet, Stax.ai creates it for you rather than failing the run.

You'll find the new option in Automation Config wherever you set the source and destination.

Improvements

• Email — The inbox composer now preserves the formatting of HTML templates instead of stripping it.

• Milestones — Plan Data columns on plan-year reports now sort, so related fields stay grouped as you scan a report.

• Reminders — Reminder schedules can no longer be saved with a follow-up interval of zero, which previously caused a schedule to behave unpredictably.

• Reminders — Reminder runs complete noticeably faster on large client lists.

Fixes

• Automations — Automated email tasks no longer stall when a workflow resolves an internal Plan Manager contact; those tasks now complete and send as configured.

• Automations — The Save a Project File automation was writing to a duplicate client directory instead of the one linked to the client; files now land in the directory set on the automation.

• Bulk Email — A send with more than one recipient option required every option to resolve, so recipients who matched only one were skipped as "Missing To field"; a recipient now sends as long as at least one option resolves, and an interrupted send no longer delivers a second copy.

• Data Fields — Selecting an existing data field could display a different field than the one chosen; the correct field is now shown.

• To Do — The status filter's "exclude" option had no effect on the projects list; excluded statuses are now correctly filtered out.