How to Configure Platform Settings
Admin guide
This page is for administrators with write access to Platform Settings. Changes here affect every user on the instance.
What is it?
Platform Settings holds the configuration that applies to the whole instance rather than to a single object. It's organized into sections you navigate from the left, and a separate Maintenance Scripts console for diagnostics.
- One settings record per instance.
- Each section is independent; fill what you need and save.
- The AI section is split into LLM Config and Observability sub-tabs.
Before you start
- You need write access to Platform Settings.
- For SSO, have your identity provider details ready (endpoints, client IDs, secrets).
- For the AI assistant, have your LLM provider credentials ready.
Settings Sections
General
| Field | What it controls |
|---|---|
| Maximum File Size | Largest file (in MB) a user can upload. |
| Allowed File Extensions | Comma-separated list with leading dots (for example, .csv, .xlsx, .pdf). |
| Allowed Python Imports | Comma-separated modules permitted in object definitions and scripts. Used when validating definition syntax. |
| Allow file upload as Input Source in Table Registry | Toggle. Lets users register tables from an uploaded file. |
Configure Logins
| Field | What it controls |
|---|---|
| Allowed Login Options | Multi-select of Password, OTP, Enterprise SSO, Google, Microsoft. At least one is required. |
| Whitelisted Domains | (Shown when a federated login is enabled) Comma-separated email domains allowed to sign in via SSO. Blank allows any domain. |
| Default Role | (Shown when a federated login is enabled) The role assigned to users provisioned on first SSO login. |
Branding
| Field | What it controls |
|---|---|
| Financial Institution Type | (Optional) Credit Union or Bank. |
| Brand Name | (Optional) The name shown in the product. |
| Primary Logo | Logo for light backgrounds (SVG or PNG). |
| Reverse Logo | Logo for dark backgrounds (SVG or PNG). |
Hooks
A Data Lake - Pre Read Hook lets you run Python before the platform reads from a Data Lake source. The hook has access to location and username. Leave blank for no hook.
Governance
Require Supporting analysis for approvals and reviews is a toggle. When on, every approval and review must have a job attached.
Warning
Turning this on cancels all open review requests that have no job attached. You are asked to confirm before saving.
Default Reports
For each simulatable object type (Quality Profile, Data Element, Feature, Model, Dataset, Policy), pick the reports that should be selected by default when a simulation is run on that object type.
Single Record Review Format
Define display formats keyed by Alias. Each row pairs a unique alias with a Format (0, 0.00, 0.000, 0.0000, 0%, or 0.00%). These control how values render in Single Record Review output.
AI
The AI section has two sub-tabs.
LLM Config sets the assistant's provider and model:
| Field | What it controls |
|---|---|
| Provider | Azure OpenAI, OpenAI, Anthropic, Google, AWS Bedrock, or Google Vertex AI. |
| AI Bot Name | Display name for the assistant. |
| Authentication | Provider-specific. API key for most; AWS region and access keys for Bedrock; GCP project and location for Vertex AI; endpoint and API version also required for Azure OpenAI. Saved keys are masked; use Change key to replace. |
| Model Name / Deployment Name | The model to use (labeled Deployment Name for Azure). |
| Temperature | 0 to 2 (default 0.7). |
| Max Tokens | 1 to 128000 (default 4096). |
| Enable streaming responses | Toggle (default off). |
Use Test connection to verify the configuration before saving.
Observability wires up Langfuse tracing: toggle Enable Langfuse Tracing, then provide Public Key (pk-...), Secret Key (sk-..., masked once saved), and an optional Host (defaults to https://cloud.langfuse.com).
Maintenance Scripts (Console)
The Maintenance Scripts console runs Python diagnostics against the instance. Predefined scripts include:
- List of Python Dependencies: show installed packages and versions.
- Clear Cache: clear the platform's memoized cache.
- Test DB Schema: check whether the database schema is up to date.
- Change username: rename a user across the platform, including audit columns.
You can also run arbitrary Python. Press Ctrl+Enter to execute.
Warning
The console executes code directly against the running instance. A bad script can destabilize the system. Treat it as an irreversible action.
What's next
- Manage Users and Configure Roles, which the login and default-role settings here depend on.
- Configure an Approval Workflow, which the Governance setting interacts with.