On this page

By default your customers sign in to their support portal with an emailed link or code. For a company that runs its own identity provider, such as Microsoft Entra ID, Okta or any other OpenID Connect provider, you can also offer Sign in with company account on that company's portal. Its people then sign in with the work account they already use. The emailed link can stay beside the button, or you can require company sign-in so it is the only way in.

It takes three steps:

  1. Add a connection to the company's identity provider under Settings → Service Desk → Single sign-on, and register DevStride's return address with the provider.
  2. Test the connection. A connection is switched on only once its test passes.
  3. Offer it on the company's portal from the company record.

SAML isn't supported yet

Company sign-in uses OpenID Connect. Providers that only offer SAML can't be connected yet.

Before you start: what the company's IT team sets up#

Ask the company's identity-provider administrator to register DevStride as an application in their directory and send you three things: the issuer, a client ID and a client secret. The return address they need to register is shown in DevStride once you've added the connection (step 1 below), so you may go back and forth once.

  • Use the company's own directory. The issuer must be one organization's own, over https. DevStride refuses shared issuers that let anyone claim any address: personal Google accounts (accounts.google.com) and Microsoft's common, organizations and consumers endpoints. For Microsoft Entra the issuer looks like https://login.microsoftonline.com/<tenant-id>/v2.0.
  • The provider must say the email is verified. DevStride matches a signed-in person to a contact by email address, so it only accepts an address the provider marks as verified. Most providers do this on their own. Microsoft Entra does not by default. In the app registration, open Token configuration → Add optional claim → ID, and add both email and xms_edov. Without them, every sign-in is refused.
  • Single-tenant, web application. In Entra, choose "Accounts in this organizational directory only" and a Web platform.

1. Add a connection#

Go to Settings → Service Desk → Single sign-on and choose Add connection:

Field What to enter
Display name What customers see on the button, for example "Contoso (Microsoft)".
Issuer The provider's OpenID Connect issuer, exactly as it publishes it.
Client ID and Client secret From the application the company registered. The secret is stored encrypted and never shown again.

A connection can belong to one company, or be shared by every portal of your desk.

After you save, the connection shows its return address, ending in /auth/oidc/callback. Add every address it lists to the application's redirect URIs at the provider.

2. Test the connection#

Choose Test. DevStride contacts the provider and checks that it answers as an OpenID Connect provider at that issuer. When it does, you'll see The provider answered. The connection is on.

  • Only a tested connection can be offered. A new connection stays a draft until its test passes.
  • Changing the issuer, client ID or scopes switches it back to a draft. Test it again before any new company can use it. Pointing it at a different provider also needs the client secret entered again: the old secret is never sent to a new provider.
  • A failed re-test doesn't cut anyone off. Portals already using the connection keep working, but no other company can be pointed at it until a test passes again.
  • Disable a connection to stop it being used, and Enable it when you're ready. It comes back on only if its last test passed.
  • A connection a company is using can't be deleted. Change that company's sign-in setting first.

3. Offer it on a company's portal#

Open the company under Service Desk → Companies. In its Portal sign-in section, set Sign-in to Company sign-in beside email and pick the connection. The company needs a portal address first. Once it works for the company's people, you can switch to Company sign-in only (see below).

Pair it with Domain-restricted

The portal's access mode still decides who may come in. If the portal is Open, anyone the provider vouches for can enter, and DevStride warns you. For a company's internal help desk, set the access mode to Domain-restricted with the company's email domains.

What customers see#

On the portal's sign-in page, a Sign in with display name button appears above the email form. A customer clicks it, signs in at their company's provider, and comes back signed in to the portal.

  • The first time, DevStride links the person to the contact with the same verified email address, or adds them as a new contact of the company if there is none.
  • After that, they sign in through their provider each time. A company sign-in lasts about 12 hours, shorter than the week an emailed sign-in lasts, so access follows the company's own directory closely. Access is also re-checked on every visit, exactly as for emailed sign-in.
  • If the sign-in fails (the provider refused it, the address wasn't verified, or the portal's access mode doesn't let them in), the customer sees a short message and, unless company sign-in is required, can use the emailed link instead. The reason isn't shown to the customer.

Require company sign-in for a portal#

Set the company's Sign-in to Company sign-in only to make the company's identity provider the only way in to that portal. Before you save, DevStride says what will happen: Only company sign-in will open this portal. People signed in by email are signed out on their next click, and emailed sign-in links and codes stop working.

Check first#

  • The connection is tested. You can only require company sign-in on a connection that is switched on and passed its latest test, so a failing connection can't lock the portal.
  • The company's directory sends their people's email address. DevStride matches people by the verified address their provider reports. For Microsoft Entra, the app registration needs the email and xms_edov optional claims (see Before you start), and each person needs an email address in the directory.
  • The access mode still decides who comes in. The portal's access mode is applied to the address the provider reports. For a company's own help desk, use Domain-restricted with the company's domains.
  • Pick a quiet time and tell the company's people that the portal now opens with their work account.

What happens when you switch#

  • The email form disappears from that portal's sign-in page. Only Sign in with company account is shown.
  • No emailed sign-in links or codes are sent for that portal, and links and codes sent earlier stop working.
  • Anyone signed in by email is signed out on their next click, and can sign back in with their work account.
  • People already signed in with their work account stay signed in.
  • Other companies' portals are unaffected.

How to undo it#

Set Sign-in back to Company sign-in beside email or Email only. It takes effect on the next request: the email form comes back and new emailed links work again.

When someone leaves the company#

  • Removed from their company's directory: they can't start a new sign-in from that moment. A session they already hold lasts up to about 12 hours.
  • To end their access now, block the contact in DevStride. Their open session ends on their next click.
  • Unlinking a contact's company sign-in (in the contact's Company sign-in section) only resets how they're matched: their next company sign-in is matched again from scratch. It doesn't end a session they already hold. To cut off access now, block the contact.

Signing out#

People can sign out of the portal with Sign out in the portal header. That signs them out of the portal only, not out of their company account, so on a shared computer the next company sign-in may go straight through as the same person. Remind people to sign out of their work account too on a shared computer.

The risk to plan for#

While company sign-in is required, the portal opens only through the company's identity provider. If the provider is down, or the connection's client secret expires, nobody from that company can sign in until it's fixed or you switch the portal back to Company sign-in beside email. Put the secret's expiry date in your calendar, and renew it with the company's IT team before then: edit the connection and enter the new secret.

Merging and erasing contacts#

A contact's company sign-in follows them:

  • Merging a contact into another moves their sign-in to the surviving contact. See Merging duplicate requesters.
  • Anonymizing a contact removes their company sign-in along with everything else. If the same person signs in through their provider again later, they start as a new contact. See Erasing a requester.

Permissions#

Company sign-in has its own permission, Manage Portal SSO. It covers adding, editing, testing and removing connections, and choosing which companies' portals offer company sign-in. It requires Access Settings. The Portal sign-in section on a company also needs Manage Requesters.

The Owner and the Admin role hold it. Other roles and the Service desk agent template don't include it, so an administrator must add it to a role. Whoever holds it decides which identity provider can vouch for a company's people, so grant it as you would an administrator permission.

See Service Desk permissions.

Powered by DevStride