# Platform Configuration Before integrating with LiveID+, organizations must complete the platform setup by providing essential information about their structure and processes. The following details are required for platform configuration: 1. Organization parameters 2. Organization process details 3. Operators list Namirial S.p.A. is responsible for the platform setup, configuration, and deployment. ## Organization Registration Every organization must be registered in the LiveID+ system. In addition to the organization's name and an email address for communications, the following parameters can be configured: | **Property** | **Description** | **Default** | | --- | --- | --- | | **name** `required` | Name of the organization. | | | **alertEmailExt** `required` | An external email address to receive notifications about session limits and system alerts. | | | **logo** | The logo of the organization to be shown in the left upper corner (jpg or png image 50x300). | | | **website** | The website of the organization. | | | **opBackground** | An image to be shown as background for the operators, or `"blur"` for a blurred background. | | | **theme** | The CSS theme to be applied to the organization's interface (to be discussed with Namirial). | | | **maxDaysKeepingFiles** | The retention period (in days) for video identification files. Files are deleted from the LiveID+ storage after this period. | 10 | | **maxOperatorLoggedSameTime** | The maximum number of operators allowed to be logged in simultaneously (Leave empty for no limit). | | | **maxOperatorActiveTime** | The maximum duration (in seconds) an operator can remain active without performing any actions. | 86400 | | **operatorCallAnswerTimeout** | The time (in seconds) an operator has to answer an assigned call. | 30 | | **maxSecondsUserWaitingForAnswer** | The maximum time (in seconds) a user waits for an operator's response before the call is closed. | 300 | | **maxCallIdleSeconds** | The maximum time (in seconds) an operator can wait for a user to connect before the session is terminated. | 60 | | **maxConferenceIdleSeconds** | The maximum duration (in seconds) a conference call can remain idle before being terminated. | 60 | | **waitingAudioCfg** | Configuration for the audio or music played while a user waits for an operator. | | | **operatorDocuments** | A list of links of documents that operators can access from the admin panel. | | | **skip_operator_AVrecTest** | If set to `true`, skips the audio/video recording test during the network and media test. | false | | **deactivateQueueInfo** | If set to `true`, disables the display of queue position information for customers. | false | ## Processes Each registered organization must define one or more processes. A *process* is a configured workflow that defines: - The sequence of modules presented to the customer during a video identification session (e.g., document capture, liveness check, operator review). - Operational details such as which external services to invoke upon successful identification. Process configuration is managed by Namirial. Contact the support team to define or update processes for your organization. ### Process Types LiveID+ supports two main process types: - **Live process**: A video identification session conducted in real time with a live operator. The customer connects to the platform, performs a compatibility test, and is routed to an available operator for the video call. - **Self-identification process**: An automated identification flow where the customer completes the required steps (document capture, liveness check, etc.) without interacting with a live operator. This can be used standalone or combined with a live process as a fallback. When using the `service-start` API, the `id_process` parameter selects a single process, while the `id_process_live` and `id_process_self` parameters can be used to let LiveID+ automatically determine which process to use based on predefined criteria (to be discussed with Namirial during setup). ## Operators Operators handle video identification calls for organizations. Each operator must be assigned to an organization before managing its calls. Each operator can manage calls for multiple organizations. Upon each login, they can select which organizations they want to receive calls from. ### Operator Roles There are two basic types of operators: - **Standard Operator**: Limited access to the administration panel; can answer calls and modify personal information. - **Administrator Operator**: Has all standard operator privileges plus the ability to register new operators and access the reporting panel. Each operator within an organization must be assigned a *role*, which defines the types of video-recognition processes they can manage. Organizations with multiple processes can restrict operators to just a specific subset of them or grant access to all available workflows. ### Operator Assignment to Calls Calls can be routed to operators in two ways: - **Automatic routing**: The call is assigned to the first available operator for the organization. - **Direct assignment**: The call is routed to a specific operator using `id_operator2Call`, `email_operator2Call`, or `extId_operator2Call` parameters. If the specified operator does not answer within the timeout, the call is terminated (it is **not** reassigned to another operator). ## Accessing LiveID+ Resident operators can log in to the administration panel via the following links: - **TEST Environment**: https://liveid.test.namirialtsp.com/app/service-login/ - **PRODUCTION Environment**: https://liveid.namirialtsp.com/app/service-login/ ### External Login For organizations maintaining a list of operators, a Single-sign-on strategy can be arranged based on SAML or OAuth/OpenID. See the [Authentication](/it/products/liveidplus/enterprise/get-started/authentication) section for more details.