Insights & updates from our experts
Responsibility for Maintaining Service Instances
The access rights that the Configuration Manager role offered for registering and updating service instances has been transferred to the Service Level Manager role. Several Xurrent customers requested this adjustment and their reasoning seems sound.
These organizations give many of their specialists the ability to maintain the CMDB, but they want to limit the ability to maintain the service instances to just a few people; specifically the people who manage the services, service offerings and SLAs.

Note that configuration managers can still place a service instance record in Edit mode to add or remove configuration items. An overview of all the roles and the access rights they provide can be found in the online help.

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)











