Insights & updates from our experts
Since the introduction of the Account Designer role, there is no longer a practical reason to limit the access rights that the Account Administrator role provides.
This role is now able to create and edit the following record types:
- Request
- Knowledge article
- Problem
- Change
- Change template
- Task template
- Project template
- Project task template
- Configuration item
- Invoice
Regular Xurrent users should no longer have the Account Administrator role linked to their person record. Ideally, this role should be given only to special person records that are used to access Xurrent when the setup of the account needs to be adjusted, or to provide the access rights needed by integrations.
Because a person record to which the Account Administrator role has been given can give itself all other roles of the account, this role may as well have all the access rights that these roles provide. Ultimately, therefore, the goal is to ensure that the Account Administrator role, as well as the Directory Administrator role, can create and update all record types in their 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)














