Why it matters
The project consequence
This is an access-continuity issue, not a feature announcement. Bluebeam says Legacy SSO is disabled after 31 August 2026. Users can still use the standard email-and-password flow, but company identity-provider access remains unavailable until SSO 2.0 is set up.
What to do next
Three useful checks
- 01
Confirm whether the organization still uses Legacy SSO and identify the Bluebeam account owner.
- 02
Test standard sign-in and the password-reset route with a small user group before a project team needs emergency access.
- 03
Complete SSO 2.0 migration with the identity team and check supported identity-provider and SCIM requirements on the live Bluebeam guidance.
Boundary to watch
Do not let the headline outrun the source.
Bluebeam’s page describes the general transition. Each organization still needs to confirm its account configuration, support route and access policy with Bluebeam and its identity team.
Go deeper