How to add SSO to Appbot?

Contents

Single Sign-On (SSO) allows your team to log in to Appbot using your organization’s identity provider. This simplifies access management and improves security by allowing users to authenticate with their existing company credentials.

Appbot supports SSO via SAML-compatible identity providers, including Okta, Azure AD, OneLogin, Google Workspace, and others.

SSO is included in the Premium plans and is available to be purchased as an add-on to Large plans.

Configuring SSO

We recommend the following rollout process when adding SSO to Appbot:

Configure SSO in Appbot.
Test the setup with one user.
Confirm the login process works correctly.
Use the Migrate Users option to move the rest of your team to SSO.

This approach minimizes disruption and ensures your SSO configuration is working before enforcing it across the entire account.

To configure SSO for Appbot please follow our guides for your chosen platform:

SSO Errors

If you encounter an error while setting up or using SSO, our support team can help investigate the issue.

What does a Team Conflict error mean?

If you try to migrate a user to SSO and see a Team Conflict error, it means the user’s email address is already associated with another Appbot account.

This usually happens when:

The user is currently a member of another Appbot team, or
The user previously created an Appbot trial account using the same email address.

Because an email address can only belong to one Appbot account at a time, the system cannot migrate the user to your team’s SSO until the conflict is resolved.

If you encounter this error, please contact Appbot support and include the email address of the affected user. Our team can help resolve the conflict so the user can be successfully migrated.

I am receiving a different SSO error message

If you receive a SSO error that is not the team conflict, please contact support and include the following details to help us diagnose the problem quickly:

The step in the setup process where the error occurred (for example configuring SAML settings, testing login, migrating users, or signing in via SSO)
The exact error message you received – a screenshot of the error, if possible would be great
The SSO provider you are using (for example Okta, Azure AD, Google Workspace, etc.)
The SSO type or protocol being used (for example SAML)
The email address of the affected used.

Providing this information will help our team identify the issue and resolve it as quickly as possible.

FAQ about Appbot SSO

Can I test SSO before migrating my entire team?

Yes. We recommend testing SSO with a single user before migrating your entire team.

When SSO is enabled, existing users will continue to log in with their email and password until they are migrated to SSO. This allows you to confirm that the configuration works correctly before moving everyone to SSO.

Once the setup has been confirmed, you can migrate the rest of your team.

What happens to users who are not migrated to SSO?

Users who have not yet been migrated will continue using their existing email and password login.

This allows teams to roll out SSO gradually. Once a user is migrated, they will be required to sign in through your SSO provider.

Can I invite new users after enabling SSO?

Yes. Appbot supports Just-in-Time (JIT) provisioning when using SSO.

With JIT provisioning, user accounts are automatically created in Appbot the first time a user signs in through your identity provider. This means a user does not need to be manually invited or create an Appbot account before accessing the platform.

As long as the user has access to the Appbot application in your identity provider, their account will be created automatically when they log in via SSO.

Does it support Just-in-Time User Provisioning

Appbot supports Just-in-Time (JIT) provisioning when using SSO.

With JIT, user accounts are automatically created in Appbot the first time a user signs in through your identity provider. This means a user does not need to create an account in Appbot before they are added to SSO.

What happens if SSO is unavailable?

If SSO is enforced and your identity provider is unavailable, users may not be able to log in until the provider is restored.

For this reason, many teams choose to test SSO thoroughly before migrating all users, ensuring the configuration is correct and stable.

What identity providers does Appbot support?

Appbot supports SAML 2.0 compatible identity providers, including:

If your organization uses a SAML-compatible provider not listed above, it should still work with Appbot.

If you need any further assistance, don’t hesitate to contact us with any questions or check out our FAQ section here.

Was this article helpful?

Yes No

About The Author

Tracy Cordwell

Tracy is Head of Customer Experience at Appbot. She has worked in the software industry for over 20 years in many different roles, including as a Product Manager, UX Designer and Project Manager. She has worked on hundreds of digital products from mobile apps, websites, e-commerce and enterprise software. She holds an array of qualifications including a PgC in Product Management and UX Design, an MBA and a MPM. When Tracy is not helping Appbot customers stay ahead of the curve you can usually find her on a basketball court or buried in a book.