DRUID has the capability of identify a user via email or via mobile phone. When a user is registered trough a concrete channel type, all DRUID workflows by default will be process using the registry user channel.

Traditional register

DRUID can choose different channel types to use in a traditional register of a user. You can configure a register with a communication channel via email or sms.

The registry channel type is configured through Cockpit tool, and is configurable by entry point.
In a registry entry point configuration of your app, you have to mark the data channel as ‘main’, it indicates that any DRUID workflow process through this entry point, will use this communication channel with user.

Email communication channel

Configure email as main communication channel, in selected entry point of an app, in Cockpit tool:

Identity channel. Email

User access to a DRUID traditional register page. DRUID will request him the email to complete his register:

After complete the register form, the user will receive an email with a link to complete his register or like an alternative the confirm code:

Identity channels. Communication emailMobile phone communication channel

Configure mobile phone as main communication channel, in selected entry point of an app, in Cockpit tool:

Identity channel. Mobile

User access to a DRUID traditional register page. DRUID will request him the mobile phone to complete his register:

After complete the register form, the user will receive a sms with a link to complete his register or like an alternative, the confirm code:

sms

Activate your account with the code:11111.
This code is valid for 48 hours.

Other workflows

When a user create his account at DRUID with a specific communication channel, email or sms, rest of workflows that this user process in his life cicle at DRUID, will use this communication channel type. For example, remember password, request new confirm code…

If user wants edit at his profile the communication channel, DRUID will do a confirmation process to verify the new value of this field.