For the complete documentation index, see llms.txt. This page is also available as Markdown.

Glossary

This glossary clearly and simply explains the terms and concepts used in the IDV Suite manual, to help you understand and use the platform with ease.

A

  • Authentication: Verification process of the identity of a user, device, or system before allowing access to an application or service. It can be carried out through passwords, biometrics, tokens, or other security factors.


D

  • Dashboard: Main view of an application that centralizes relevant information in the form of metrics, charts, and quick access links.


F

  • Flows: Configured sequence of steps that a user follows during an authentication, onboarding, or validation process.


I

  • AI: Technology that allows machines to simulate intelligent behavior, such as learning, reasoning, solving problems, or making decisions. It is based on algorithms that process large volumes of data to identify patterns and generate automatic responses.

  • Identity: Information that represents a user within a system, including personal data, credentials, and associated attributes.

  • Integrations: Connections between the platform and external systems to share information or automatically execute processes.


K

  • KPI (Key Performance Indicator): Metric that measures the performance of a process, activity, or system in relation to defined objectives. It is used to evaluate progress and detect areas for improvement.

  • Flows: Configured sequence of steps that a user follows during an authentication, onboarding, or validation process.


L

  • Low-code: Development approach that allows applications to be created or configured through visual interfaces and predefined components, reducing the need to write code manually.


N

  • No-code: Development approach that allows applications to be created or configured without the need to write code, using visual editors and preconfigured blocks.


O

  • Onboarding: Process of onboarding and verifying a user in an application or system. It includes steps such as registration, identity validation, acceptance of terms, and initial setup.

  • Operations: Actions or processes executed within the platform, generally associated with authentication, validation, or the use of services.


P

  • Permissions: Specific rights assigned to a role or user to access or modify features within the system.


R

  • Role: Set of permissions and responsibilities assigned to a user within a system. It defines what actions they can perform, what information they can view, and what functions they have available.


S

  • SaaS (Software as a Service): Software distribution model in which applications are hosted in the cloud and accessed over the internet, without the need for local installation.

  • SDK (Software Development Kit): Set of tools and resources that allow developers to integrate specific features into their applications (for example, authentication flows or identity validation).


T

  • Tenant: Independent instance within a multi-user platform. Each tenant represents a client or group of users with their own data, settings, and access, isolated from other tenants.

  • Token: Temporary code or credential generated by a security system that allows a user or application to be authenticated for a specific period of time.


W

  • Widget: Visual or functional component integrated into an interface to provide information or facilitate a specific action (for example, a form, chart, or interactive button).


Last updated