Configuration

Configuration is the tenant-level settings page where a tenant administrator reviews and edits tenant or product settings, and, where applicable, checks whether those settings have synced from another system such as Product Studio.

---

Where Configuration lives

Configuration is one tab among several inside your tenant’s Settings area. The other tabs you’ll see alongside it include Profile, Workspace, Security, Users, API, and Webhook. You move between them using the tab bar at the top of the Settings page — you don’t need to leave Settings to check a different section.

---

Opening configuration

1. Go to Settings for your tenant.
2. Select the Configuration tab from the tab bar.
3. Review the fields shown. What you see depends on your plan and the products configured for your tenant — some tenants will see more configuration fields than others.
4. If a sync status or last-sync time is displayed, use it to confirm whether recent changes from another system (such as Product Studio) have taken effect.

---

Editing configuration

1. Update the fields you’re allowed to change.
2. Save your changes.
3. If a field is read-only or grayed out, it’s likely managed elsewhere — for example, a setting that is owned by Product Studio and pushed into your tenant rather than edited directly here.
4. If sync status is shown on the page, check it again after saving to confirm the change registered.

---

Worked example

A tenant administrator at a credit union has just published an update to a personal loan product in Product Studio — raising the maximum loan amount on a personal loan product from $20,000 to $25,000. To confirm the change reached the tenant’s live configuration, the administrator:

1. Opens Settings and selects the Configuration tab.
2. Looks for the sync status or last-sync indicator on the page.
3. Confirms the timestamp reflects the recent Product Studio update rather than an older date.

If the sync indicator hasn’t updated, the administrator knows not to assume the new $25,000 limit is live for applications yet, and follows up before communicating the change to underwriters.

---

Use case

A lending operations team manages a personal loan product through Product Studio, and that product’s settings are meant to flow into each tenant’s live configuration automatically. Before telling underwriters that a new credit policy or product limit is in effect, the operations lead checks the Configuration tab for that tenant to confirm the sync status shows the change has propagated — rather than assuming the Product Studio publish alone means the tenant is updated.

---

Best practices

• Check the Configuration tab after any change is made upstream (for example, in Product Studio) rather than assuming it applied immediately.
• If a field appears read-only, don’t try to work around it — it’s likely intentionally managed from another part of the platform.
• Confirm you’re viewing the Configuration tab for the correct tenant before making changes, since Configuration is tenant-scoped.

---

Unclear / not confirmed by current sources

• The exact list of configuration fields available, and how they differ by plan or product, is not documented in the available source. Do not assume any specific field beyond what appears on your tenant’s page.
• What happens if a sync fails, times out, or shows an error state is not confirmed.
• Whether the sync status is a manual refresh or updates automatically is not confirmed.
• Which settings are always read-only versus editable, and which are “managed elsewhere,” is not fully specified.