> For the complete documentation index, see [llms.txt](https://docs.facephi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.facephi.com/docs.facephi-en/products/facephi-intelligence-platform/modulos/configurator.md).

# Configurator

Configurator allows you to create, configure, and manage the processes that run through FIP solutions.

<figure><img src="/files/c410bd5bc6d1d47384c66c04cb6f30e58479b5ad" alt=""><figcaption></figcaption></figure>

From this module you can:

* View the available processes.
* Create onboarding and authentication processes.
* Configure their components and parameters.
* Add and configure challenges.
* Save processes as drafts.
* Publish and unpublish processes.
* Clone existing processes.
* Archive and delete processes, depending on your permissions.
* View the information needed to integrate a process.
* Test a published process using demo mode.
* Manage other available configurations for your tenant and your role.

{% hint style="info" %}
Changes made in Configurator do not affect new executions until the corresponding configuration is published.
{% endhint %}

***

## How it is organized

The main section of Configurator is **Processes**.

From there you can access the list of processes and open each one to view or modify its configuration.

Each process is defined, among other elements, by:

* Its type.
* The environment in which it runs.
* The template used.
* Its components.
* The parameters of those components.
* The configured challenges.
* Its status.

Some additional configurations may be available depending on the contracted features and the permissions of your profile.

***

## Access and permissions

The available actions depend on your role and the permissions associated with your profile.

Depending on your permissions, you can:

* View processes.
* Create processes.
* Edit them.
* Clone them.
* Publish or unpublish them.
* Archive them.
* Delete them.
* Run them in demo mode.
* Access additional configurations.

When an action is not available to your user, it may remain hidden or disabled.

{% hint style="info" %}
Published processes cannot be modified directly. If you need to change their configuration, you must first unpublish them when you have permission to do so.
{% endhint %}

***

## View processes

**Processes** shows the processes available in the selected environment.

<figure><img src="/files/1083eadf654941b129c6104f45e535a9b9818aba" alt=""><figcaption></figcaption></figure>

Each item in the list lets you identify the process, see its status, and access the available actions.

### Search and filter processes

Use search to locate a process by name.

When available, use filters to narrow the results according to criteria such as:

* Status.
* Process type.
* Environment.
* Template.

Applied filters are shown above the list and can be removed individually.

Select **Clear all** to remove them all.

### Results

Each process can show information such as:

* Name.
* Description.
* Process ID.
* Process type.
* Environment.
* Template.
* Status.
* Version.
* Creation or modification date.

Depending on the view, indicators related to its use may also appear.

### Open a process

Select the process or the available view action.

Its details will open with the corresponding configuration.

The actions you can perform from the details depend on its status and your permissions.

### No processes

When there are still no processes, the list shows an empty state.

Select **Create process** to configure the first one.

New processes will appear in this list once created.

***

## Process statuses

Status indicates where a process is in its life cycle.

### Draft

The process is being configured and is not yet available for new executions.

You can modify it and save changes until it is ready to be published.

### Published

The process is published and can be used to start new executions.

The published version is immutable.

To make changes, you must first unpublish it when you have permission to do so.

### Archived

The process has been removed from regular work, but it is kept in the system.

Depending on your permissions, you can restore or delete it.

***

## Create a process

Select **Create process** from the list.

Creation begins by defining the main characteristics of the process.

<figure><img src="/files/6cf886aafda69c8325fb61ff849a11d53744c89c" alt=""><figcaption></figcaption></figure>

### Select the process type

Select the type of flow you want to configure.

It can be:

* **Onboarding**
* **Authentication**

The selected type determines the templates and components that will be available.

### Select the environment

Select where the process will run.

Available options may include:

* Web.
* iOS.
* Android.

The environment determines the compatible components and configurations.

### Select a template

Select the template that will serve as the initial configuration.

The template defines a base combination of:

* Components.
* Validations.
* Parameters.
* Dependencies.
* Challenges, where applicable.

You can then modify the elements that are configurable.

{% hint style="info" %}
Some values are determined by the process type, environment, or template and cannot be modified later.
{% endhint %}

***

## Configure a process

Configuration is organized into different sections depending on the process type and the selected template.

<figure><img src="/files/f2ec16d861fd2617b62aaf73c562abfe7cc76a05" alt=""><figcaption></figcaption></figure>

It may include:

* General information.
* Terms & Conditions.
* Components.
* Parameters.
* Challenges.
* Additional technical configuration.

### Editable fields

Editable fields let you modify the configured value.

Each field may have:

* An initial value.
* A specific format.
* A permitted value range.
* A minimum or maximum length.

The system validates the information before saving or publishing.

### Read-only fields

Some values are shown but cannot be modified.

These fields represent configurations determined by:

* The component type.
* The template.
* The environment.
* The system itself.

{% hint style="info" %}
A field not being editable does not mean it is incomplete. Some values are part of the component's internal configuration and are shown only as a reference.
{% endhint %}

### System-managed values

Some parameters needed to run the process may not appear in the form because the system manages them automatically.

You do not need to configure them manually.

### Value validation

Fields accept only values compatible with their configuration.

If you enter a value outside the permitted range or with an incorrect format, correct it before saving or publishing.

***

## Terms & Conditions

Terms & Conditions lets you configure the information the user must accept during the process.

The configuration may include:

* Title.
* Description.
* Time available to complete the step.

Only **one Terms & Conditions component can exist within the same process**.

If one already exists, you will not be able to add a second equivalent component.

***

## Configure components

Components determine the captures, checks, and interactions that are part of the process.

The template includes an initial configuration that you can adapt within the allowed limits.

### View a component

<figure><img src="/files/83dca6bebf9ac0975a95abe4ca545d97af49edc7" alt=""><figcaption></figcaption></figure>

Each component shows its name, status, and the available actions.

Depending on the component, you may find:

* **Edit**
* **Disable**
* **Restore**

Available actions depend on its configuration and its relationships with other components.

### Edit a component

Select **Edit** to open its configuration.

Modify the available parameters and save the changes.

Select **Cancel** to close the edit without applying them.

Some parameters may be shown as read-only because their value is determined by the system.

### Disable a component

Select **Disable** when you want to keep the component within the configuration but prevent it from taking part in execution.

Before disabling it, the system checks whether there are other components that depend on it.

If it can be disabled, confirm the action.

The component remains visible in the configuration as disabled.

### Dependencies between components

Some components need others to be active in order to work properly.

For example, a validation may need a previous capture to have the information it must analyze.

When you try to disable a component with dependencies, the system informs you of the affected elements.

<figure><img src="/files/fda0ced96baebe10b761eeeb3bd69f3b58c0fe52" alt=""><figcaption></figcaption></figure>

Depending on the relationship between them:

* The action may be blocked.
* It may be necessary to disable other components as well.
* The system may request additional confirmation.

{% hint style="warning" %}
Always review the affected components before confirming a disable. The change can modify the Flow the user will experience.
{% endhint %}

### Restore a component

Select **Restore** to re-enable a disabled component.

The system checks its dependencies before restoring it.

When other related components are also disabled, it may be necessary to restore them to recover the configuration correctly.

Depending on the case, the interface may allow:

* Restoring only the selected component.
* Also restoring the components needed to satisfy its dependencies.

Review the information shown before confirming.

After restoring it, the component takes part in the process execution again.

### Required components

Some components are needed for the template to work properly.

When a component is required:

* It cannot be disabled, or
* The action appears blocked.

The interface indicates when a configuration is necessary to keep the Flow valid.

***

## Configure challenges

Challenges let you add additional checks to the process.

<figure><img src="/files/98bff049d7f17896d21db3c6b46af518b6603664" alt=""><figcaption></figcaption></figure>

The available ones depend on:

* The process type.
* The template.
* The environment.
* The enabled features.

### Add a challenge

Select the challenge you want to include and complete the available parameters.

Each challenge may have its own:

* Fields.
* Initial values.
* Ranges.
* Limits.
* Dependencies.

### Edit a challenge

Select **Edit** to modify its parameters.

The system validates that the new values are compatible before saving.

### Disable a challenge

When this action is available, select **Disable** to keep the challenge configured without running it.

The challenge remains visible, but it stops taking part in the process while it is disabled.

### Restore a challenge

Select **Restore** to add it back into execution.

The system restores its configuration and checks the required dependencies.

### Execution order

When the process contains several challenges, their order determines the sequence in which they can run.

If the interface allows you to change that order, arrange the challenges according to the expected behavior before publishing.

***

## Save a process

You can save the configuration while working on it without needing to publish it.

Select the available save action.

The process remains in **Draft** state until it is published.

<figure><img src="/files/b8ed43b9c015e47b07228df98cad6f41bbf47e3c" alt=""><figcaption></figcaption></figure>

### Validation errors

A process can be saved as a draft even if it still needs adjustments.

However, certain errors prevent it from being published.

Before publishing, review:

* Required fields.
* Values out of range.
* Required components.
* Dependencies.
* Incomplete configurations.

{% hint style="info" %}
Save and publish are different actions. Saving preserves the configuration; publishing makes it available for new executions.
{% endhint %}

***

## Clone a process

Select **Clone** when you want to create a new process from an existing configuration.

The clone is created as a process independent of the original.

Use this option when you want to reuse a configuration as a starting point without modifying the existing process.

After cloning it:

1. Open the new process.
2. Review its identifying data.
3. Check the inherited components and parameters.
4. Review the challenges and dependencies.
5. Make the necessary changes.
6. Publish the new process when it is ready.

Changes made in the clone do not affect the original process.

{% hint style="info" %}
Before publishing a cloned process, review its entire configuration. A configuration valid for one process may need adjustments before being reused in another context.
{% endhint %}

***

## Publish a process

Publishing makes a version of the process available for new executions.

Select **Publish** when the configuration is complete.

<figure><img src="/files/d3880126ae74b1bab33d0d749f72ac5a1bd8bc11" alt=""><figcaption></figcaption></figure>

### Pre-publishing validations

Before allowing publication, the system checks that the process is valid.

It can verify:

* Required fields.
* Required components.
* Dependencies.
* Configured values.
* Challenges.
* Other template requirements.

If there is any problem, correct the indicated items before trying again.

### Confirm publication

Select **Publish** and review the confirmation.

After publishing:

* The process changes to **Published**.
* An immutable version is created.
* That version becomes available for new executions.
* The published configuration cannot be edited directly.

***

## Process versions

Each publication generates a version of the configuration.

Operations keep the reference to the version with which they were executed.

This allows a previous operation to continue representing exactly the configuration used at that time, even if the process changes later.

### Modify a published process

To modify a Published process:

1. Unpublish it, when you have permission.
2. Make the necessary changes.
3. Save the configuration.
4. Validate the process again.
5. Publish it.

The new publication generates a new version.

Previous operations remain linked to their original versions.

{% hint style="info" %}
History and visual comparison between versions are not part of the current functionality.
{% endhint %}

***

## Unpublish a process

Select **Unpublish** to prevent the process from continuing to be used to start new executions.

<figure><img src="/files/e20ebabf1711678e8f939cf6790e4cf85d76b5eb" alt="" width="282"><figcaption></figcaption></figure>

This action may be limited to certain roles.

Before confirming, review the impact of removing the process from publication.

After unpublishing it:

* New executions cannot be started with the removed version.
* The configuration can be modified again when your permissions allow it.
* Already started or recorded operations keep the information about the version used.

When you republish the configuration, a new version will be generated where appropriate.

***

## Archive a process

Select **Archive** when you want to remove a process from regular work without deleting it permanently.

The system requests confirmation before completing the action.

After archiving it:

* The process no longer appears among active processes.
* Its configuration is preserved.
* Previous operations remain linked to their versions.

Depending on your permissions, you may later be able to restore an archived process.

***

## Delete a process

Deletion is available only when the status and your permissions allow it.

Select **Delete** and review the confirmation modal.

After confirming, the process is no longer available for regular management.

The evidence and references needed to maintain the traceability of previous operations are not modified.

{% hint style="info" %}
Deleting a process is an irreversible action from the interface. Use Archive when you need to remove it without losing the possibility of recovering it.
{% endhint %}

***

## Process details

The details allow you to view a process configuration and perform the available actions.

It may display:

* Name.
* Description.
* Process ID.
* Process type.
* Environment.
* Template.
* Status.
* Version.
* Components.
* Challenges.
* Associated technical information.

### Copy the Process ID

Select the copy icon next to the Process ID.

Use this identifier when you need to reference the process during an Integration or a technical query.

### Available actions

Depending on the status and your permissions, from the details you may find actions such as:

* Edit.
* Clone.
* Publish.
* Unpublish.
* Archive.
* Delete.
* Demo.

***

## Test a process in demo mode

Demo mode allows you to run a published process before using it in a real Integration.

<figure><img src="/files/d2b0d2dba870eee397b1761d495ca8433a3a6e00" alt="" width="254"><figcaption></figcaption></figure>

The action is only available when:

* There is a Published Version.
* Demo mode is enabled.
* Your profile has the necessary permissions.

### Open the demo

Select the corresponding action from the process.

A modal will open with:

* Process information.
* QR Code.
* Instructions to start the demo.

### Web Demo

To run a Web process:

1. Open the indicated demo URL from a mobile device.
2. Use the camera to scan the QR Code.
3. Complete the process.

### Mobile Demo

For a Mobile process, use the corresponding demo app and scan the QR Code when prompted.

### QR Code validity

The QR Code associated with the process:

* It is persistent.
* It can be reused.
* It does not expire.
* It is not consumed after a run.
* It is not invalidated when the modal is closed.
* It does not need to be regenerated.

The same QR Code runs the Version **Published** that is active at that time.

If you publish a new Version, the QR Code uses that new Version.

### What happens when you unpublish

When the process does not have an active Published Version, the QR Code stops starting new demos.

It is not necessary to generate another code.

When a Published Version exists again, the same QR Code can be used again.

{% hint style="info" %}
The QR Code identifies the process, not a specific execution. That is why it can be used several times as long as there is a published version.
{% endhint %}

***

## Additional configurations

Depending on the contracted features and your profile permissions, Configurator can include other configuration areas.

These surfaces can manage elements that affect more than one process.

Only consult the options available in your tenant and avoid modifying global configurations without first reviewing their impact.

***

## Create and publish a process

As a reference, the usual Flow for preparing a process is:

1. Open **Processes**.
2. Select **Create process**.
3. Choose the process type.
4. Select the environment.
5. Choose a template.
6. Complete the required information.
7. Review Terms & Conditions.
8. Configure the components.
9. Check the dependencies.
10. Configure the challenges.
11. Save the process.
12. Correct any validation errors.
13. Select **Publish**.
14. Confirm the publication.
15. Check the process using demo mode.
16. Use the Process ID and the necessary technical information to perform the Integration.

Before publishing, review the complete Flow and check that the configuration matches the experience you want to offer the user.