With single sign-on, people open Hives with your organisation’s own sign-in, such as Entra ID, Okta, Google Workspace or another SAML 2.0 provider. They click Hives in their portal, intranet or colleague app and they are in, with no second login. Or they choose single sign-on on your hive’s sign-in page and come straight back.
Who can do this: Admins, once Hives has made single sign-on available for your hive. Ask help@hives.co or your Hives.co contact to make it available. Until then, you don’t see it in your settings.
You do the setup in Hives together with whoever runs your organisation’s sign-in. This article is for you. Send them Single sign-on: what your IT team needs.
Open the setup
- Open Menu > Admin > Hive.
- Stay on the Access tab.
- In the Sign-in section, find Single sign-on. It shows where it stands: Not set up, Not tested, Tested, off or On.
- Click Set up (or Change, once a provider is saved).
The single sign-on page has six sections, in the order you need them.
1. For your IT team
Three values your IT team enters in your organisation’s sign-in:
| Value | What it is |
|---|---|
| Sign-in address (ACS URL) | Where your provider sends people back to Hives after they sign in. |
| Entity ID | Hives’ name in your provider. |
| Metadata link | All of the above in one file, for providers that can read it. |
Click Copy next to each one and send them to your IT team, with the article for them. The values stay the same if your hive is renamed, so a setup never breaks for that reason.
2. Your provider
Your IT team gives you something back. Enter it in one of three ways:
- Metadata link: a web address your provider publishes. In Entra ID it is the App Federation Metadata Url of the Hives application.
- Upload file: the metadata file, if your IT team sends you one.
- Enter by hand: the Issuer (Entity ID), the Sign-in address and the Certificate. Paste the whole certificate, including the lines
-----BEGIN CERTIFICATE-----and-----END CERTIFICATE-----.
Click Save provider. Hives then shows the issuer, the sign-in address and the certificate’s fingerprint and expiry date. When a certificate expires within 30 days, it says so. Ask your IT team for the new one before then, and click Replace provider to save it.
If Hives can’t use what you entered, it says why under the field, for example “Hives couldn’t open that link. Check it, or upload the file instead.”
3. Who is who
Each person is known by decides what Hives uses to tell people apart. It has to be something your provider always sends and that never changes for the person.
- Email address: use this when everyone has a work email address of their own.
- Employee ID: use this when some people have no work email, or share one login on a shared computer. Each person still gets their own account in Hives.
Under What your provider sends, each field in Hives has the name of the attribute your provider sends for it: first name, last name, email, employee ID, and any profile fields your hive uses, such as job title and department. Hives fills in usual names to start with. Change a name if your provider uses another one, and leave a field empty if your provider sends nothing for it.
Click Save in the bar at the bottom.
4. Test sign-in
Before anyone else uses single sign-on, sign in once yourself.
- Click Run a test sign-in. Your provider opens in a new tab.
- Sign in there as you normally do.
- Come back to the single sign-on page. It shows the result.
When the test works, you see The test worked and the account you were recognised as. Under What your provider sent, you see every attribute with its value, and which Hives field it fills. Not sent lists the fields nothing filled. Fix the names under What your provider sends, or ask your IT team to send the missing attribute, and test again.
When the test doesn’t work, Hives says why, for example “Your provider’s signature wasn’t accepted. Check the certificate.”
The test doesn’t sign you in and doesn’t change your account. If you change the provider later, run the test again.
5. Turn it on
- Under Button name, write what the button on your sign-in page says, for example the name your colleagues know your sign-in by. The default is Single sign-on.
- Turn on Let people sign in with single sign-on. The switch stays off until a test sign-in has worked.
From now on:
- Your hive’s sign-in page shows the button first, above the other sign-in methods you have on.
- Links to Hives in your organisation’s portal sign people straight in.
Your other sign-in methods stay as they are. Turn them off under Access if you want everyone to use single sign-on.
6. Sign-in log
The Sign-in log shows the last 100 sign-ins with single sign-on, kept for 90 days: when, what happened and who. When someone can’t get in, look here first.
| What happened | What it means |
|---|---|
| Signed in | It worked. |
| No access to Hives | Single sign-on is switched off for your hive, so the person wasn’t let in. |
| Access turned off | An Admin has turned off the person’s access to your hive. |
| Not meant for this hive | The provider’s answer was for another app. Check the Entity ID and sign-in address in your provider. |
| Link expired | The answer came too late. Check the clock of your provider. |
| Signature not accepted | The certificate doesn’t match. Replace the provider with the current certificate. |
| No identity sent | Your provider didn’t send the attribute in Each person is known by. |
| Used twice | The same answer came twice and was refused. |
| Not started by Hives / Couldn’t be read | Something in the answer was wrong. Check the setup with your IT team. |
| Test sign-in | A test from this page. |
What happens when people sign in
- The first time, Hives looks for the person’s account in this order: an account already linked to your single sign-on, then a member of your hive with the same employee ID, then an account with the same email address, but only when that address is on your hive’s allowed domains or already a member of your hive. If none fits, Hives makes a new account.
- Nobody’s account is taken over. If the email address belongs to an account outside your hive, the new account doesn’t get that address.
- Everyone signs in as a Member. Your provider decides who may reach Hives. You give Admin and Manager roles in Hives, as before.
- Names are set when the account is made and never overwritten afterwards. Employee ID and profile fields follow your provider at every sign-in. A profile field your provider fills can’t be changed in Hives. See Profile fields.
- Someone whose access is turned off stays out until an Admin turns it on again.
- A single sign-on session opens your hive only. If the person is also in another organisation’s hive, they sign out and sign in there in that hive’s own way.
- Signing out of Hives signs out of Hives only, not out of your organisation’s sign-in.
Common questions
Do people need to do anything?
No. Tell them Hives is in your portal, or that the button on your sign-in page now says what you called it.
Can a person have both an email code login and single sign-on?
Yes. When Each person is known by is Email address, and the address is on your allowed domains or already a member, they end up in the same account either way.
We use Microsoft or Google already. Why single sign-on?
Sign in with Microsoft and Sign in with Google need a work email address for each person and send only names and email. Single sign-on works with an employee ID too, starts from your own portal, and can fill in job titles and departments.
Something isn’t working and the log doesn’t help
Contact help@hives.co with the time of the sign-in and what the log says.
More: Hive settings: access, sign-in and the login page · Trouble signing in