Skip to main content

Single Sign On for Your Careers Website Editor

Single sign on: One work login for your whole team. Illustrated Happydance cover.

 

Platform feature

With single sign on, your team logs in to the careers website editor with the same work login they already use, through Okta or Microsoft. For careers websites only for your own employees, the whole site can sit behind that same login.

By the Happydance team. Updated November 2026.

A careers website editor is a door into your employer brand. The fewer passwords behind that door, the safer it is, and the easier your team finds it to use.

Definition: Single sign on

A way for people to log in to one system with the work login they already use for others, so there is no separate password to remember or manage.

How careers website single sign on works for your team

Your team logs in to the careers website editor with the same work login they already use, through Okta or Microsoft. Other login providers can be set up on request. For careers websites only for your own employees, we can put the whole site behind that same login.

Single sign on is included in every Happydance plan: Essential, Plus and Premium. Compare the plans.

Editor

Your work login

Your team logs in to the careers website editor with the same work login they already use, through Okta or Microsoft.

Flexible

Other providers on request

Other login providers can be set up on request.

Whole site

Employee-only sites

For careers websites only for your own employees, we can put the whole site behind that same login.

Free toolSee your careers website the way candidates doRun the free scan. It takes about two minutes, and you will see what is already working and what could work harder.Find out nowIllustration of a score gauge with the word Scan

Why it matters

  • Your team has one fewer password to remember, share or write down
  • Access follows the rules your IT team already runs for work logins
  • New editors can be given access through the system you already use
  • Your security team sees a familiar way of working, not a new one
  • Editors spend their time on the careers website, not on resetting passwords

Login decides who gets in. Roles decide what they can do

Single sign on answers one question: is this person one of ours? Roles and permissions answer the next one: what may they change? The careers website CMS lets you decide who can edit and who can publish, and keeps an audit log of who changed what, and when. Use both. A global brand team, a regional editor and a recruiter should not all have the same keys.

Three questions of access, and what answers each.
QuestionAnswered byWhere to read more
Is this person one of ours?Single sign on, with your work loginThis page
What may they edit or publish?Roles and permissions in the CMSCareers website CMS
Who changed what, and when?The audit logCareers website CMS

A careers website only for your own employees

Not every careers website is for outsiders. An internal mobility site is for people who already work for you, and it should not be open to the world. For careers websites only for your own employees, we can put the whole site behind that same login, so only people who can log in with their work account can see it. See the internal mobility site.

What candidates see

For a public careers website, nothing changes for candidates. They do not sign in to browse jobs or to apply. Single sign on is for your own people.

Protect the story, and the people who tell it

Your careers website holds your brand's most honest conversations. It deserves the same care you give other work systems. A familiar login is a small thing that keeps the right people in and the wrong ones out.

Truth without structure falls flat. Structure without truth falls apart.

Bryan Adams, Sell The Truth

A quick truth test for this page:

  • Do the right people have access, and only them?
  • Would you know when someone who left no longer has it?
  • Is protecting the site as routine as protecting email?

Single sign on readiness checklist

Single sign on readiness checklist

Work through these with your IT team before your editors first log in.

1. Name your login provider

Okta or Microsoft are supported. If you use another, ask us, because other login providers can be set up on request.

2. List who needs editor access

Name each person and their job: edit, publish, or look only.

3. Match roles to people

Single sign on decides who gets in. Roles and permissions decide what they can change.

4. Decide if the whole site needs a login

For a careers website only for your own employees, we can put the whole site behind the same login.

5. Ask how access ends

Ask us how access ends when a colleague leaves, and test it with a leaver during your first month.

6. Tell your editors

A short note on how to log in and who to ask for help.

Created by Happydance as a thinking aid. It carries no data from you.

Keep exploring: four pages to read next

Pick the page that matches where you are in your search. Each one links back to the others, so you can move between guides, your ATS, comparisons and plans.

Guide

Career site providers

Compare career site providers on the same criteria, before you shortlist. Read the guide.

Your ATS

Careers website for Greenhouse

See how a Happydance careers website works with Greenhouse. See the Greenhouse page.

Compare

Paradox alternative

A fair, sourced look at Paradox for teams comparing options. Read the comparison.

Plans

Mid-market careers website

Plus, from $40k per year, for teams ready to level up. See the plan.

Free preview: six checks to run in any CMS demo

A free preview. Use it as it is, or take the full pack.
CheckDemo testWhat good looks like
RolesCreate an editor who can change one page and nothing else.Permissions set by role, in a few clicks
ApprovalsSend a change for approval and publish it as the approver.A clear step between drafting and live
Version historyShow who changed a page, when, and what changed.A readable history for every page
RollbackRestore the previous version of a live page.One action, with no developer
LanguagesAdd a language and edit it as a local editor.Local editors, one structure
Phone checkPreview the change on a phone before it goes live.A real mobile preview

Want the full pack? Download it free

The full checklist goes deeper on every check, with demo questions you can reuse. It is free on the download page, with no form to fill in. When you are ready, you can book a demo when you are ready.

Questions to ask any supplier about single sign on

  1. Can my team use our existing work login for the editor, and with which providers?
  2. What if we use a login provider that is not on your list?
  3. Can an employee-only careers website sit wholly behind our login?
  4. How do roles and permissions work alongside single sign on?
  5. How is access removed when someone leaves the team?

Add these to the RFP template, and ask us how access ends when a colleague leaves.

What is single sign on for a careers website?

A way for your team to log in to the careers website editor with the same work login they already use, so there is no separate password to manage.

Which login providers does Happydance support?

Your team can log in through Okta or Microsoft. Other login providers can be set up on request.

Can a whole careers website sit behind a login?

Yes. For careers websites only for your own employees, we can put the whole site behind that same login.

Which plans include single sign on?

Single sign on is included in every Happydance plan: Essential, Plus and Premium.

Do candidates need to sign in?

No. On a public careers website, candidates do not sign in to browse jobs or apply.

Does single sign on control what an editor can change?

No. Single sign on decides who gets in. Roles and permissions in the CMS decide what each person can edit or publish.

See it on your own jobs

Book a demo and we will show you this feature, and the rest of the platform, on a careers website running on a phone.

Book a demoScan your careers website