Identity¶
Introduction¶
In the Configuration > Identity page, you can choose the method users of your app will use to log in:
-
Jitterbit: Selected by default. This is the built-in user management solution where users set to Active in the Employees module can log in to the app.
- App Builder handles user password management with emails defined in the Configuration > Email Templates page for this setting.
-
Office 365: App Builder supports Microsoft Azure Active Directory (Azure AD) authentication for organizations that use it. To log in to the app using this authentication type, users need:
-
An account with the organization's Azure AD.
-
A user with the same email associated with Azure AD set to Active in the Employees module.
-
-
Google: App Builder supports Google authentication for organizations that use it. To log in to the app using this authentication type, users need:
-
A personal or company Google account.
-
A user with the same email associated with the Google account set to Active in the Employees module.
-
-
Okta: App Builder supports Okta authentication for organizations that use it. To log in to the app using this authentication type, users need:
-
An Okta account on the Okta Identity Platform.
-
A user with the same email associated with the Okta account set to Active in the Employees module.
-
A configured Okta App Integration.
-
Profiles can then be set for each user in in the Employees module to define what level of access they have in your app.
Switching Login Systems¶
Caution
It is recommended that you set up your organization's Azure AD instance to support App Builder apps before changing this setting to Office. See Azure AD Identity Configuration for App Builder Apps for more information.
To switch between login systems, click an authentication provider button and then click Save. (When choosing Okta, additional configuration fields are shown.)
