Skip to main content
You connect Rise once at the MSP level, with your own OAuth application in Rise.

​
Before you start

  • You need a Rise role with the Manage OAuth applications permission. The Owner and Admin roles have it.
  • Neo acts as the Rise user who creates the application. Rise shows that user only the people and time off they may see, so create the application with an Owner or Admin account, or with a user who has the organization-wide time-off calendar permission. Otherwise dispatch sees only that user’s own team.

​
1. Create the application

1

Open OAuth applications

In Rise, open People > Settings > OAuth applications and click Create application.
2

Fill it in

Name it Neo, and choose the Confidential client type. Neo does not use a redirect URI.
3

Check the scopes

For dispatch around time off, check time_off:read and employees:read. Check more only for the jobs you plan:
4

Copy the client values

Save the application and copy the Client ID and the Client Secret. Rise shows the secret once.

​
2. Save it in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the Rise People card, under HR & Business Apps.
2

Save the application

Enter the Client ID, the Client Secret and the Scopes you checked, separated by spaces (for example time_off:read employees:read), and click Save settings. Neo signs in to Rise before saving, so a wrong value, or a scope the application does not have, is rejected straight away.
From then on, AI dispatch reads booked time off from Rise; Round Robin does not. When you add a scope to the application in Rise, add it to the Scopes field in Neo too. If the secret is rotated or the application is deleted, Neo stops reaching Rise. Save the new Client Secret, or a new application, in Neo.

​
3. Turn Rise People on per agent

The Dispatch Ticket action needs no agent setting. A dispatch agent that uses Get Technician Context needs Time Off at Read Only or more to see booked leave. For an agent that answers who is away, works approvals or reads HR data, open the agent, go to the Integrations section, and pick an access profile for the Rise People block, or set each area yourself: Each area can be Disabled, Read Only or Read / Write. See Rise People API for the profiles.