How To: Give Users Access When Your Account Uses SSO

If your Schema App account uses Single Sign-On (SSO), new people do not get access by resetting a Schema App password. Access is controlled by your company identity provider (for example Microsoft Entra ID / Azure AD, Okta, or OneLogin), and Schema App creates or links the user when they sign in successfully with SSO.

TABLE OF CONTENTS

• What to do for a new user
• If sign-in fails

What to do for a new user

1. Ask your identity provider (IdP) administrator to assign the person to the Schema App application (or the security group that grants Schema App access) in your company IdP.
2. Have the user sign in with SSO using one of the methods your company chose:
   • Identity Provider initiated: Sign in to your company portal, then open the Schema App app tile.
   • Service Provider initiated: Go to https://app.schemaapp.com/login, enter the work email, and complete sign-in with your company IdP when redirected.
3. On the first successful SSO sign-in, Schema App creates the user on your account (if they are not already there) using the name and email from your IdP, and signs them in.

Note: After SSO is enabled for an account, users should not use the email/password form for day-to-day access. Use your company IdP tile or the SSO redirect from the Schema App login page.

If sign-in fails

• Confirm the person is assigned to the Schema App application (or group) in the IdP.
• Confirm they are using their work email and the SSO path above (not a forgotten Schema App password).
• If the IdP shows an error (for example a Microsoft Entra error page), share the exact message or a screenshot with your Schema App Customer Success Manager.

For an overview of IdP-initiated vs Schema App–initiated login, see Single Sign-On (SSO) - Solution Description.

Need help enabling SSO for the first time, or changing who can access Schema App? Contact your Schema App Customer Success Manager or support@schemaapp.com.