Insights & updates from our experts
When someone has the Specialist role of a Xurrent account, this person is able to edit requests in that account. This person can, for example, update the status of a request from ‘Assigned’ to ‘Accepted’, which causes his/her person record to be selected in the Member field of the request. But if this specialist is not a member of a team in this account, or any other account that has access to the request, the Team field becomes empty.

To explain why that happens, a warning now gets displayed. This warning informs the specialist that he/she does not belong to a team to which the request can be assigned. The specialist can then apply a service instance of an account in which the specialist is a member of a team. Alternatively, the specialist can assign the request to a team that is allowed to take responsibility for the request, and if needed, ask to become a member of this team.

A Note From the Road: What SPARK Taught Me About Time
During the second SPARK event in Antwerp, I stood at the back of a training room and watched a customer build a custom integration with our new iPaaS, wiring Xurrent to another system in her stack that had never talked to it before. No services rep doing it for her. No statement of work, no project plan with a kickoff and a go-live date. Just a person with live beta access in her hands, connecting two systems by hand, and finishing it before her coffee went cold. A year ago that would have been a multi-week project with a budget attached. She looked up, a little surprised it had actually worked, and said something I have not stopped thinking about since. She said it just gave her her week back.

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)














