Every new agency site that integrates with DRUID can be configured completely within this module by a non-technical operator. A new agency can integrate with DRUID a site within hours, as the system supports the configuration part of the process with this panel.
List, search and Manage Apps
An App is basically a set of credentials (Client ID and password) needed by Agencies or other company vendors. Those credentials are installed in the agency app servers and managed sites, and grant access to DRUID resources, such as user registration, log in, API access, etc. This App defines apart from the credentials, all the metadata associated and configured to establish digital communications between Agency sites and their users.
The tool provides to operator the ability to list all the Apps integrated, and perform searches based on simple criterias.
If the operator is assigned to an agency, Cockpit shows only those apps that belong to the agency.
Clicking to a row of the table you access to app detailed configuration.
An entry point is a specific area in a App used for identifying an user action in a concrete point. An entry point defines a specific configuration in this point, as example different fields available in a form. Each App has at least one entry point and can have as many as the agency wants.
Entry points enrich the account lifecycle and relational interactions created by users.
Example: when a user logs-in via an entry point for one hypothetical “My awesome promotion app”, the entry point adds the related meta-information from the entry point to the interaction, such as, brand, promotion, country, platform, user typology, etc.
The entry point configuration also modifies many behaviors of the system, such as:
- Look&feel based on brand, typology or property
- Form fields requested to the user
- Texts and validations based on user typology
- Language and functionalities based on country
- Registration confirmation channel (email or SMS)
Configure an Entry Point
An entry point configuration contains basic info, fields configuration and advanced features.
Basic entry point info contains the entry point name and description, and if is the main section of the App. The main entry point is used in your app navigation, when you not specify a concrete entry point in a app action.
With this tool operators can configure the form fields that will be shown to the user that wants to do an action (register, complete data, etc.) via the entry point.
The available registration form fields are different depending on the selected country and typology, so the configuration window will filter the available fields depending on that criteria.
A main field is used to determine which mechanism will be used to confirm user registrations (email or SMS).
A field required confirmation before interact is used to determine if user needs to confirm email, sms or both before perform some digital interaction (log-in, vote, comment, etc).
Promotion, program, platform, live event… are associated to Agency App configuration in order to enrich the account lyfecicle and relational interactions created by users through this App entry point.
A work typology defines the regiter typologies group that can be managed in an entry point. Assigning a register typology to an entry point determines:
- Available fields based on typology
- Site blocking based on typology
- Terms and conditions acceptance after concrete digital action
- Opt-in checks per typology
- Text and appearance screens per typology
- Typology that will be assigned to a user after a digital action through this entry point
Role is to assign special permissions to write or read only fields through User API to an entry point. More information in User API chapter.
Restric login, restricts the login in this entry point, by work typology assigned.
Passwordless register: if you check it, the register throug this entry point will be passwordless.
2 steps registration is a special register in two steps, for example an operator register via admin, and user complete the register. For more information please send a email to DRUID product owner to receive information about LAM tool.
App basic data contains the name of your app, the app domain and the app credentials (Client ID and secret). The operator can recreate the client secret.
In this section you can download your OAuth xml credentials file, or send it to the agency contacts. When an agency app is properly configured, an operator can send the xml credentials file to agency contacts and product owner. The xml sent to the agency contacts is needed to run the DRUID SDK properly.
By default an App is activated. Deactivating agency app revokes all permissions to the available DRUID resources when the site is sunset or a security alert is reached:
In this panel you can configure the next app info:
- Brand and property are associated to Agency App configuration in order to enrich the account lyfecicle and relational interactions created by users through this App.
- SDK Version and the programmatic language of Gentesis ID used in the app integration.
- An App marked as test mode, indicates that their users and interactions are for testing, for example Cockpit excludes their data from exportation tools.
- Country of the app
- Automatic authorization avoid the visual windows that DRUID displays to user when he registers. This step is defined by Oauth protocol. By default is checked.