Identity Orchestration

A process workflow offers an optimised user experience that guides customers through a process, such as progressive profiling during the login procedure. With Identity Orchestration, you can adapt processes to different user situations or contexts quickly.

Process extensibility lets companies configure predefined process workflows in a flexible manner. This allows you to react quickly and dynamically to changes in a customer’s situation or context, even if the CIAM software is already integrated into the IT landscape.

Different contexts and situations can necessitate different workflows. The more agile and flexible a company can be in dealing with its customer requirements, the greater the potential for more revenue, greater customer satisfaction and higher capital yield.

The composable-pattern concept in nevisAdmin 4 provides several mechanisms that enable the extensibility of processes as well as the definition and adaptation of identity flows to different situations.

The idea of A/B tests in the context of CIAM is to optimise registration and login sequences for the purpose of maximising a desired result.

One possible use case could be to minimise registration cancelations and reduce the number of interested parties who begin the registration process but then fail to complete it. The question here is: why did they fail to complete?

• Was too much information requested?
• Did the system ask for an email confirmation, and did potential customers fail to respond?

It would be useful to have the ability to change the registration sequence with some hypotheses in order to test and observe whether the new version (version B) works better than version A. A percentage of the data traffic is still directed to registration A and another percentage to registration B.

Nevis customers can conduct A/B tests. This is based on a technique known as side-by-side deployment:

Consent and privacy management is extremely important for the CIAM system in the context of the European Union’s GDPR requirements.

Nowadays, large companies have dedicated systems such as Actionable Data Intelligence for GDPR analyses, OneTrust for automating applications for subject rights and many more to cover all aspects of the GDPR requirements.

Nevis provides a small but useful function for obtaining consent to the general terms of business either during the registration procedure or later in the profile management functions.

nevisIDM terms and conditions:

• Many-to-many relationships between applications and conditions
• One or more terms can be assigned to an application – like a privacy statement, legal terms, etc.
• Conversely, multiple applications can use the same terms. A consent object is created if a user accepts conditions.
• The consent object links the user to the accepted terms. It stores the current version and date of the conditions if they are accepted.

A Nevis customer can define the terms of business for each application behind the Nevis infrastructure and obtain the consent of the end user. This is then stored in the Identity Repository.

The consent and the general terms of business are accessible via the API and can be used in the profile management screens of a customer to display all the accepted GTCs for a specific user.

Customers expect to interact with companies across multiple channels (mobile, web, chatbots). Successful companies use the ubiquity as well as biometric functions along with camera and sensor functions of smartphones as omnichannel authentication keys.

Our Access app and our SDK can be used to authenticate users with native biometrics from anywhere and at any time.

• Push notification (from non-mobile)
• QR code (from non-mobile)
• Deep link for mobile channels and messengers

Large companies often have several brands with different end-user and partner target groups. Separate brand portals and logins must be available. However, it is costly and inefficient to have different CIAM systems for each brand. A better solution would be to have one standard CIAM system that can support multiple brands and customer journeys.

Nevis can support complex customer journeys for multiple brands in one standard CIAM solution. The brand support includes:

• Custom look & feel for every brand login
• Differentiated registration and authentication paths for each brand
• Differentiated privacy and consent settings for each brand and region
• Separate clients for each brand with separate administrators
• Individually branded MFA access applications with specific brand colours and fonts