Skip to content
shuffl
Get started

Searches the public product guides only. Nothing from a workspace is read, and questions are not saved.

How-to guide

Use Shuffl with JumpCloud

Connect JumpCloud to keep People current and sign everyone in, and see what Shuffl does with it.

For HR and IT administrators

Have your agent do thisPaste the prompt into Claude Code, Cursor or another agent. It follows this guide over MCP and asks before it changes anything others will see.Show the prompt
Help me with "Use Shuffl with JumpCloud" in my Shuffl workspace.

1. Read the guide: https://shuffl.ai/docs/markdown/jumpcloud
2. Add Shuffl's MCP server: https://shuffl.ai/api/mcp
   Claude Code: claude mcp add --transport http shuffl https://shuffl.ai/api/mcp
   When the browser opens, choose my workspace and allow the access the guide needs.
3. Work through the steps in order: Connect JumpCloud to People; Sign in with JumpCloud. Do what you can over MCP and tell me which steps only I can do in the browser or in Slack.

Show me what you will change and who it affects, and wait for my yes before publishing, inviting or sending anything.
On this page

App links open your signed-in workspace. Check the selected workspace before making changes.

What JumpCloud does in Shuffl

JumpCloud manages your company’s accounts and devices. Connect it to keep People current and let everyone sign in to Shuffl with JumpCloud.

You need to be a Shuffl workspace administrator, with an administrator in JumpCloud for the steps there.

Connect JumpCloud to People

  1. In Shuffl, open People, then the Sync tab. Under Add a source, choose Connect on JumpCloud.
  2. In the JumpCloud Admin Portal, open your administrator menu (top right) and choose API Settings.
  3. Generate an API key, or copy the current one. Keys expire after 90 days by default, so note when to rotate it.
  4. Paste the key into Shuffl. Shuffl checks it by listing users before saving it.
  5. Choose Connect and sync. The first sync runs straight away and says how many people were new or linked.
  6. Review the new people in People and enable access for those who should use Shuffl. A sync never turns access on.

What comes in

Shuffl reads JumpCloud once a day. Sync now on its card reads it at once. Shuffl only reads; it never changes anything in JumpCloud.

JumpCloud’s values replace People’s on every read, so fix a wrong title or manager in JumpCloud. A blank keeps what People has.

From JumpCloud into Shuffl

  • Everyone, with names and work emails
  • Job titles
  • Managers
  • Departments
  • Leavers

What it does for HR

In Shuffl

  • Managers fill the org chart, so playbook meet steps, manager to-dos and 30/60/90 plans reach the right person.
  • Departments become department groups, so Pulse, eNPS and Culture compare teams without exposing anyone.
  • Suspended or removed accounts lose their Shuffl access.
  • Mello knows each person’s title, manager and department when it answers.

Sign in with JumpCloud

  1. In Shuffl, open Settings → Workspace → Integrations → Single sign-on, choose Add connection and pick OpenID Connect. Keep the values it shows open.
  2. In the JumpCloud Admin Portal, open SSO Applications, add a Custom Application and choose to manage single sign-on with OIDC.
  3. Paste the redirect URI into Redirect URIs and the login URL into Login URL. Keep Client Authentication Type as Client Secret Basic.
  4. Turn on the email and profile standard scopes, give the user groups who should sign in access to the app, and save.
  5. Copy the client ID and client secret JumpCloud shows once. The issuer is the same for every JumpCloud organization.
  6. Add the DNS TXT record the connection shows at your DNS provider, then choose Check DNS record until it reads Verified.
  7. In a private window, choose Sign in with SSO with a work email that is in People with access enabled.

Single sign-on proves who someone is; People still decides who gets in. Set up People first, and password sign-in keeps working while you test.

Good to know

JumpCloud API keys expire after 90 days by default. Note when to rotate yours, then connect again with the new key.

JumpCloud signs only the SAML response by default, which Shuffl refuses. Sign the assertion too, or use OpenID Connect.

With your other systems

JumpCloud has no start dates and no terminated state. Connect your HR system for those, or record start dates and Employment ended in People yourself.

If it stops working

When a card reads Needs attention, JumpCloud refused Shuffl’s key or sign-in. Create a new one in JumpCloud and connect again; Shuffl replaces the stored one. A failed run changes nobody.

Disconnect stops syncing and deletes the stored key. Everyone stays in People to edit by hand.

Was this guide helpful?