Insights & updates from our experts
The buttons that allow users to select their preferred identity provider for accessing Xurrent have gotten a facelift. Their improved styling presents each single sign-on (SSO) option as a button. Each button now has the same width and includes a logo so that end users and support specialists will recognize their preferred option more quickly.

When the following code is included in the CSS injection field of the ‘Account Design’ section of the Settings console, only the SSO buttons will be visible:
.with-sso-options form,
.with-sso-options .separator,
.with-sso-options p { display: none; }

This CSS code can give account designers some ideas on how to perfect the look of the Sign In screen of their organization’s Xurrent account.

An AI SRE that knows your incidents
Most AI SREs are pattern matchers trained on public data. They know what a memory leak looks like in the abstract. They don't know that your payments-api has a flaky liveness probe everyone ignores, that the checkout team owns the retry policy, or that the last three "database incidents" were actually cache misconfigurations. That knowledge lives in your postmortems, your Slack channels, and the heads of two senior engineers.

How Long Should ITSM Implementation Really Take in 2026?
Most vendors will tell you ITSM implementation takes six months to a year — but modern, configuration-first platforms have rewritten the math entirely. See what real implementations look like in 2026, and why a long rollout is now a choice, not a given.















.webp)
.webp)

.webp)












