Skip to main content
Shift signs your teammates in through your bank’s identity provider (IdP) with OpenID Connect, and reads their identity and roles from it at each sign-in. For what your teammates see once SSO is on, see Shift with SSO.

What Shift expects from your IdP

Claims

Shift reads these claims from the identity of each user.

Role values

The roles claim carries one or more of the following values. Each one grants the Shift role of the same row. Roles do not nest: see Roles for the sections each one opens before you decide which values each user gets. You assign them in your IdP.

Send Paylead your IdP details

Send the following for each environment, Sandbox and Production.

What Paylead provides

Paylead returns a dedicated Shift URL for each environment of your Program. It replaces the standard sign-in URL.

Set up SSO

1

Register a client in your IdP

Create a dedicated client for Shift in each environment, with its own client_id and client_secret. Do not reuse the client of the Paylead WebApp: it must not send profile or email claims, which Shift needs. Use the Authorization Code flow, and note the client_id, client_secret and authentication mode.
2

Expose the claims

Make every claim listed in Claims available in the identity of each user, with the values from Role values.
3

Send the details to Paylead

Send the items listed in Send Paylead your IdP details, once for Sandbox and once for Production.
4

Test in Sandbox

Open the Sandbox Shift URL Paylead returned and sign in with SSO.
5

Repeat in Production

Run the same sign-in against the Production Shift URL once Sandbox works.
Shift opens with the sections granted by the role values your IdP sent.

What’s next

See what your teammates get with SSO

The controls Shift hides once your IdP owns accounts.

Choose the roles for a teammate

Match each job to the role values your IdP sends.