If your area has Single Sign-on (SSO) enabled, you'll see an additional section here for configuring SSO Behaviors for individual Users. If SSO is required for your Subscriber, you do not need to set individual behaviors for each user, unless you would like to allow certain users to sign-on via username and password. The value in the SSO Setting field will indicate if SSO is required or optional for your area. If you would like to change whether SSO is required or not, submit a ticket and the support team will work with your team to change that setting.

• Login Behavior - Use this field to require that individual users sign in via SSO, even if it is optional for your Subscriber. Alternatively, if SSO is required in your area, you can allow individual users to sign-in via username and password. Finally, if your area has an IDP Override set up, you can require that users sign-on via that mechanism. In this case, you also need to specify which Override they should use in the IDP Override field.
• Mobile Behavior - This field is like the Login Behavior, but sets requirements for users of the Mobile app. Because the Mobile app communicates with the server via RESTConnect, and RESTConnect's login behavior is governed by the option above, you will typically need the Mobile Behavior to be coordinated with the Login Behavior.
• IDP Override - If your area has an IDP Override set up, you can use this field to append that override onto links in system-generated e-mails. This field is also used in conjunction with the Login Behavior field when you select the "IDP Override Required" behavior. (Contact us for more details on the IDP Override functionality.)