Blog
Insights & updates from our experts
.webp)
.webp)
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.
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.
5 Mins
September 10, 2026
Incident Management
Service Management
News
Enterprise
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.
8 Mins
May 30, 2026
Service Management
Enterprise
Integrations