Sign in to RazorERP with your company’s identity provider.

With single sign-on through OpenID Connect (OIDC), your team uses the accounts and security policies you already manage. People sign in once, and your IT team controls access from one place.

Discuss this integration Browse integrations

Why teams use single sign-on

Every separate login is another password to manage and another account to remember when someone leaves. Single sign-on lets people reach RazorERP through the identity provider your company already uses, so your existing sign-in rules apply there too.

OIDC is a widely used standard built on OAuth 2.0. Security and procurement teams often ask about single sign-on during a vendor review, because it keeps authentication under their control rather than in one more application.

Who it’s for

IT and identity administrators
Security teams reviewing vendors
Operations leaders with many users and sites
Finance and compliance teams who audit access

How the workflow fits together

The business workflow this connection supports. What transfers, in which direction, and when is confirmed with you during discovery.

RazorERP

Your team · review

Single sign-on (OIDC)

STEP 01User opens RazorERPThe user chooses to sign in with your company’s account.
STEP 02Identity providerYour provider checks the user’s identity and applies your policies, including MFA.
STEP 03Identity confirmedThe provider sends a signed confirmation back through OIDC.
STEP 04User signed inRazorERP identifies the user and applies their security role.
STEP 05Access reviewedYour team manages who has access, and removes it when someone leaves.

Use cases

01One company loginFewer passwords for staff to manage.

02Your MFA and policiesMulti-factor and conditional access rules are applied by your identity provider.

03Faster offboardingDisabling someone at your provider stops new sign-ins through it.

04Security reviewsShow procurement that authentication stays under your control.

Evaluation & setup

What to prepare, and the questions we work through with your team before configuration.

What to bring

Your identity provider, such as Microsoft Entra ID, Okta, Ping Identity, JumpCloud, or Google
An administrator who can register an application
The email domains your users sign in from
How your teams map to RazorERP security roles
Whether contractors or shared stations need different handling

Questions we review with you

01Who should use single sign-on, and is it required for everyone?
02How are new users created, and who assigns their roles?
03How is access removed when someone leaves?
04Should your identity groups relate to RazorERP roles?
05What should happen if your identity provider is unavailable?
06Should any client portal users sign in differently?

Frequently asked questions

What is OIDC?

OpenID Connect is a standard way for an application to confirm who someone is through an identity provider. It is built on OAuth 2.0 and is widely supported by modern providers.

Which identity providers work with RazorERP?

Tell us which provider you use. OIDC is a common standard, and we will review your provider and its setup with you before you commit.

Does single sign-on replace multi-factor authentication?

No. It moves it. Multi-factor authentication and similar sign-in rules are applied by your identity provider when the user signs in there.

What about SAML?

Tell us if your organization requires SAML, and we will review the options with you.

Are users created automatically?

How users are created, assigned roles, and removed is reviewed with you during setup. Ask about your requirements for automated provisioning.

Do RazorERP security roles still apply?

Yes. Your identity provider confirms who the person is, and security roles in RazorERP determine what they can do.

Is the connection included in my subscription?

Commercial terms for integrations are covered in your proposal.

Discuss single sign-on for your team.

Tell us which identity provider you use and who needs access; we will review the setup with you.