Model any data, no parallel databases
An Attribute Set groups everything an identity type needs, without designing a separate database to store it.
VU ONEBackoffice
Go to production at click speed, without parallel databasesGo to production at click speed, without parallel databasesGo to production at click speed
An Attribute Set groups the full data kit that an identity type needs, from a simple field to a full address or a list, and is configured from the backoffice, without development. Configurable by business unit and account type.An Attribute Set groups the full data kit that an identity type needs, from a simple field to a full address or a list, and is configured from the backoffice, without development. Configurable by business unit and account type.Group the full data kit an identity type needs and configure it from the backoffice, without development.
THE PLATFORM
The data kit of every identity
An Attribute Set is the VU ONE unit that groups the data schemas an identity type needs: the complete information kit, defined once and reused without parallel databases.
3 schema types
Scalar, Object and Array.
Business-unit scope
Each set is associated with a business unit and an account type.
100% backoffice
Create, filter, edit, query and delete, without development.
Optional identifier
Any set can be marked as an identifier, with its own matching strategy.
Organizations that trust us to model the data of each identityOrganizations that trust us to model the data of each identity
Benefits
Why teams choose VU to configure identity attributes
No development, from the backoffice
Create, filter, edit, query, and delete: the full lifecycle of an attribute is managed from screens, not from a development project.
As simple or complex as the data needs
From a single field to a complete address — street, city, postal code — or a list, with the exact schema for each case.
Fits every business unit and account
Each business unit configures its own attribute sets, depending on whether the account belongs to a customer, a service, or the workforce.
Model any data, no parallel databases
An Attribute Set groups everything an identity type needs, without designing a separate database to store it.
No development, from the backoffice
Create, filter, edit, query, and delete: the full lifecycle of an attribute is managed from screens, not from a development project.
As simple or complex as the data needs
From a single field to a complete address — street, city, postal code — or a list, with the exact schema for each case.
Fits every business unit and account
Each business unit configures its own attribute sets, depending on whether the account belongs to a customer, a service, or the workforce.
Key features
How identity attributes are configured
Attribute Set
groups the schemas that represent a characteristic, condition, or business policy: the information kit an identity type needs to operate.
Scalar, Object, and Array schemas
from an atomic field — text, number, boolean — to grouped data such as an address or lists with their own quantity and uniqueness rules.
Identifier and matching strategy
any set can be marked as an identifier for verification or authentication, defining whether all attributes must match or one is enough.
Scope by business unit and account type
each set applies according to the account type — customer, service, or workforce — and its subtype: local, social, or federated.
Configurable owner level
define whether the data lives at the identity level or at the account level, according to who actually owns it.
Compatible with CRMs and SCIM
schemas automatically generate forms and are compatible with CRMs and the SCIM protocol.
How it works
What is under the hood
Step 1: Define the attribute schema
Step 1
Choose whether it is a simple field (Scalar), grouped data such as an address (Object), or a list (Array), with its validation rules.
Industries
Ideal for these sectors
Banking and financial services
Model regulatory attributes for each customer type without duplicating the data model by product.
Government
Define the exact attribute set each procedure needs, from citizen to public official.
Retail and gaming
One attribute set per account type — player, buyer, affiliate — without parallel databases.
Background screening
Model the attributes of each type of check —employment, credit, criminal— without duplicating the data model per product.
Identity, authentication and fraud prevention, unified
Configurable claims and attributes is part of VU ONE, the platform that unifies identity verification, authentication and fraud prevention in a single SDK.
Learn about VU ONEFrequently asked questions
It is a group of attribute schemas that represents a characteristic, condition, or business policy: the data kit an identity type needs to operate.
No. Schemas and sets are created, filtered, edited, and deleted from the backoffice, without development projects.
From a simple field — text, number, boolean — to grouped data such as an address (street, city, postal code) or lists, such as phone numbers or roles.
Yes. Each set is associated with a business unit and applies according to the account type — customer, service, or workforce — and its subtype.
It becomes usable for verification or authentication, with a matching strategy that defines whether all attributes must match or whether one is enough.
Not at the moment: once marked as an identifier, it remains permanent. This function is planned for future versions.
Model identity the way your business needs itModel identity the way your business needs itModel identity the way your business needs it
Configure attributes and identifiers without touching a database or opening a development project.
Configure attributes and identifiers without touching a database or opening a development project.
