Appearance
Product Studio
Last updated: 2026–08-20
Product Studio is where you build and manage the products your tenant offers — for example Personal Loan, Auto Loan, or BNPL. It controls the product catalog, the application form each product uses, and the branding customers see when they apply. Products built here are used in applications, pricing, and rules. In the sidebar it sits under Workflows.
What you can configure here
Products. Each product has a name, a version number, an owner, and a status. A product’s status shows whether the current draft is in sync with what was last published, and whether it has at least one published version. A product becomes eligible to launch only once it has a published version. Products can also be marked active or inactive.
Versions. A product can have multiple versions over time. One version is marked as the default. Each version has its own description and its own record of who last modified it and when.
Themes. A theme is a branding preset — logos (dark, light, favicon), a background image, and custom styling — that you apply to one or more products. A theme can be shared across several products at once, and a tenant can turn on white-label branding.
Application Wizard. This is the form builder behind each product’s application. It lets you lay out fields in rows, set field types (text, checkbox, list, document upload, and others), mark fields required, and set validation rules such as minimum/maximum values, character length limits, regex patterns, age ranges, and date ranges. You can also make one field’s visibility depend on the answer to another field — for example, showing a “Co-signer income” field only when “Do you have a co-signer?” is answered “Yes.”
Worked example
A tenant admin at a credit union is building a new product called Personal Loan Express.
- In Product Studio, the admin creates a new product and names it “Personal Loan Express.” This creates version 1 as a draft.
- The admin opens the Application Wizard for this product and adds fields: loan amount, requested term, employment status, and a checkbox “Do you have a co-borrower?”
- The admin sets a co-borrower income field to show only when the co-borrower checkbox is checked.
- The admin publishes version 1. The product’s status now shows the draft as in sync with the published version, and the product becomes launchable.
- The admin marks the product active so it becomes available for applications.
If the admin later edits the form again — say, adding a new disclosure field — the product’s status will show the draft is out of sync with the last publish, until it is published again.
Use case
A credit union wants one consistent look — logo, colors, background — across its Personal Loan and Auto Loan products, without configuring branding separately for each one. The admin creates a single theme in Product Studio, uploads the credit union’s logo and background image, and applies that theme to both products. Any product added to the theme picks up the same branding.
Best practices
- Publish a product version before attempting to launch it. A product only becomes launchable once at least one published version exists.
- Use versions to make changes safely: edit the draft, review it, then publish when it’s ready, rather than editing a live published version directly.
- Keep only one version marked as default per product.
- Apply a shared theme when multiple products need the same branding, instead of configuring logos and colors on each product separately.
- Use conditional field visibility (Show When logic) for fields that only apply in specific situations, such as co-borrower details, to keep the application shorter for applicants who don’t need them.
- Toggle a product to inactive rather than deleting it if you need to stop offering it temporarily.
In this section
- Product list – View and understand products.