Business metadata
Store application-specific identifiers or customer relationship data on a Kinde record.
Kinde · Const
Custom properties
Custom properties are user-defined fields for Kinde users, organizations, and applications. They store business-specific data and can be exposed in tokens as custom claims when configured as public.
How it works
Custom properties are user-defined fields attached to users, organizations, or applications. They store business-specific data, can be grouped into categories, and may be exposed in tokens when configured as public properties and selected during token customization.
Key points
- Use properties to add business-specific data beyond Kinde’s built-in profile fields.
- Custom properties can capture application identifiers, marketing details, or customer relationship data.
- Categories group related fields under a heading in a user, application, or organization record.
- The documented property types are Boolean, single-line text, and multi-line text.
- Property definitions can be maintained through the dashboard or the Kinde Management API.
- Properties can supply custom claims when included in token configuration.
Common mistakes
- Choose the property key carefully because Kinde does not allow it to be changed after creation.
- A property must not remain private if you want to include it in tokens.
- Property keys must be unique within the business.
Example: Custom property configuration
// No runnable SDK declaration is provided on the documentation page.
The documentation describes configuring custom properties in the Kinde dashboard rather than exposing a code-level const declaration.
When to use it
Organized profile data
Group related custom fields for easier viewing in records.
Token claims
Pass selected custom values between systems through tokens.
Interview questions
QWhat are Kinde custom properties used for?
Custom properties are configurable fields for users, organizations, or applications. They let a business store data beyond Kinde’s standard profile fields.
Follow-up: How would you expose one to an application? Make it public, then select it while customizing the relevant token.
QHow is a custom property configured?
A property is created in Kinde under Settings > Data management > Properties. Its configuration includes a name, unique key, visibility, target entity, category, and type.
Follow-up: Which property types are documented? Boolean, single-line text, and multi-line text.
QHow do custom properties reach tokens?
Public properties can be selected for access, ID, or M2M tokens according to the application type and token type. The selected value is then delivered as token data.
Follow-up: Where does the value appear? Token customization documentation shows it under an entity-specific properties claim, with the value represented by a v field.
Related
Custom claims and data with propertiesAdd and manage custom data with propertiesCustomize tokens using propertiesProperty categoriesKinde Management API