Blog
Insights & updates from our experts
.webp)
.webp)
Four new action options can be selected for a personal access token or an application to scope what their permissions in Xurrent. These new options concern the ability to import and export the Xurrent records that are registered in an organization’s Xurrent account.
The following actions can now be selected to define the scope:
- Import – Create – dictates whether or not the scope allows imports to be started.
- Import – Read – dictates whether or not the scope allows the progress of imports to be monitored.
- Export – Create – dictates whether or not the scope allows exports to be started.
- Export – Read – dictates whether or not the scope allows the progress of exports to be monitored and the download links of export files to be retrieved.
Note that without explicitly specifying that importing and exporting is allowed, the scope will not permit these actions to be performed for any Xurrent records. When a scope allows imports and exports, this is allowed for all Xurrent record types, i.e. requests, people, time entries, projects, etc.
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