Platform Defaults Introduction

Platform Defaults is a workspace-wide configuration surface that lets an Admin set the default values Qualytics uses when a new source datastore, container, or operation is created. These defaults replace the values Qualytics ships with and take effect automatically across the platform, so new assets inherit your governance choices without any per-datastore configuration.

What Are Platform Defaults?

Platform Defaults are the starting values Qualytics uses whenever a specific setting is not explicitly set at a more granular level. Instead of relying on Qualytics' shipped defaults, an Admin can replace them with values tailored to how your organization wants data quality to be managed.

Platform Defaults cover three groups:

• Observability: how volume and freshness are tracked, and whether AI-generated observability checks are created automatically when tracking is on.
• Profile: how much effort the AI puts into generating checks during a profile operation, and whether those checks activate immediately or start as drafts.
• Scan: the maximum number of individual record anomalies that a single check can create before they are rolled up, and the maximum number of source examples stored per anomaly to the enrichment datastore.

Where to Find the Tab

The Defaults tab lives in Settings between Integrations and Security, alongside Connections, Tokens, Audit, and Status. Once opened, the page presents a left-rail navigation between the three groups (Observability, Profile, Scan), a Save button per group, and a side card that summarizes the order of precedence.

Why Platform Defaults Matter

Every setting Qualytics uses at operation time is resolved through a precedence chain. Without Platform Defaults, the fallback at the bottom of that chain is a value hard-coded by Qualytics. With Platform Defaults, an Admin controls that fallback, which means:

• New datastores inherit your governance defaults from creation.
• New operations use your preferred AI Effort level and rollup behavior unless someone explicitly overrides them.
• With one opt-in click at save time, current defaults can be pushed to every existing datastore (and, for observability defaults, every container), replacing any per-asset customizations.

Next Steps