Single Sign-On (SSO)

You can enable Single Sign-On (SSO) so users can log in using their existing login credentials with your organization. This streamlines access management and adds an extra layer of security for your organization. Users only need a single login,...

Many Identity Providers (IdPs), including Google, Microsoft Entra ID, OneLogin, and Okta, require the Service Provider (SP) Metadata from your organization to properly configure their custom SAML application settings. This metadata contains...

Google Single Sign-On (SSO) lets users access multiple applications and services with their Google account—no need to manage separate passwords. You can integrate Google SSO to streamline user access and enhance security across your...

Microsoft Entra ID is an Enterprise identity platform that provides Single Sign-On (SSO), multifactor authentication, and conditional access—making it simple to connect with your organization. To get started, make sure SSO is enabled on your...

You can easily set up Single Sign-On (SSO) using OneLogin in your organization. This allows your team to log in with their OneLogin credentials in your organization, giving you greater control over account access and security. Simply connect your...

You can connect Okta’s Single Sign-On to your forms in just a few steps. To get started, make sure SSO’s enabled in your organization and that you have an Okta admin account. Once it’s set up, your team can log in quickly and securely using...

Single Sign-On (SSO) lets users in your organization sign in securely through your identity provider. In some cases, you may need multiple SSO configurations — for example, when different teams or partners use separate systems such as Okta,...

You can configure multiple instances of various SSO providers within your organization, offering unmatched flexibility. Multiple SSOs are advantageous if different teams within your organization rely on distinct authentication systems from...

Single Sign-On (SSO) enables users in your organization to log in securely and efficiently using your organization's identity provider. You can configure multiple instances of the same SSO provider. This flexibility is particularly beneficial for...

You can make sure even guest users sign in through SSO. It’s a simple way to keep tighter control over who accesses your forms, especially when you’re working with collaborators outside your team. Just enable the setting in your SSO...

Single Sign-On (SSO) lets users access multiple apps with one set of credentials—but when something breaks, it can slow things down for everyone.  Common issues like login errors, misconfigured settings, or security mismatches can...

When setting up Okta Single Sign-On (SSO), you’ll need to configure Attribute Statements as part of your application settings. These statements tell Okta which user details to pass to your SSO Prefill settings in your organization. They help...

You can prefill forms using data from Google SSO. To get started, you’ll first need to set up SAML Attribute Mapping. This ensures user details—like the name, email, and phone number—are passed to your form fields correctly. Once...

When configuring OneLogin Single Sign-On (SSO), setting up parameters is a crucial step in your SSO application settings—especially when enabling SSO prefill in your organization. This process ensures that key user attributes, such as name,...

With Microsoft Entra ID SSO Prefill, you must configure the User Attributes & Claims settings to populate user data into your forms automatically. This step ensures a seamless, secure, and efficient form-filling experience by reducing manual...

In order to set up SSO Prefill for an already configured AD FS Relying Party Trust, please follow the steps below. What would you need? AD FS Server with working SAML 2.0 SAML Application for your organization Management Permissions...

Enabling Single Sign-On (SSO) in your organization centralizes authentication, but some of your licensed users may also need to log in using their email address and password. This guide walks through the steps required to enable this option in the...

This guide walks you through configuring SCIM and role provisioning between Okta and your organization to automate user management and streamline access control. Before setting up SCIM, make sure you have already configured SAML Single Sign-On...

Just-In-Time (JIT) Access is a security mechanism that limits high-risk permissions—such as admin or privileged roles—so they are not permanently assigned to users. Instead, a user receives those permissions only for a short, approved time...

Users can restrict Form access to people with Single Sign-On (SSO) credentials within your organization. This way, users will sign in once through your trusted Identity Provider (IdP), making access simple for them and secure for your...

Users can restrict Tables access to people and require Single Sign-On (SSO) credentials within your organization. This way, users will sign in once through your trusted Identity Provider (IdP), keeping access simple for them and secure for your...

Users can restrict PDF access to people and require Single Sign-On (SSO) credentials within your organization. This way, users will sign in once through your trusted Identity Provider (IdP), keeping access simple for them and secure for your...

Users can restrict Inbox access to people and require Single Sign-On (SSO) credentials within your organization. This way, users will sign in once through your trusted Identity Provider (IdP), keeping access simple for them and secure for your...

Users can restrict Report access to people and require Single Sign-On (SSO) credentials within your organization. This way, users will sign in once through your trusted Identity Provider (IdP), keeping access simple for them and secure for your...

Users can restrict Board access to people and require Single Sign-On (SSO) credentials within your organization. This way, users will sign in once through your trusted Identity Provider (IdP), keeping access simple for them and secure for your...

Users can restrict App access to people and require Single Sign-On (SSO) credentials within your organization. This way, users will sign in once through your trusted Identity Provider (IdP), keeping access simple for them and secure for your...