Insights & updates from our experts
Working in text fields is now considered user activity. To be clear: when a user has been inactive for a certain time, he or she must log in again. This time is the ‘Idle session timeout’ and it is configurable in the ‘Security’ section of the Settings console. This is an important security setting that could, however, sometimes interfere with a user’s work. Up to now, user activity was defined as saving a form or navigating to a different record. When someone was working on a single record for a long time (on a complex automation rule or a very large UI extension for example) this work could be lost. Not anymore.
As long as a user makes at least one change in a text field per configured duration of the idle session timeout, his or her session will not expire. This way, our users can take their time working on long and complicated tasks that can’t be saved halfway through.

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)











