Blog

More Action Options Available to Scope OAuth Tokens

January 23, 2021

Carlyn Manly

1 Min Read

Click To Explore

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.

Import and export actions included in scope for an application that integrates with 4me

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.

Partners

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.

3 Mins

July 1, 2026

Service Management

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