---
id: ADR-PFM-QRY-014
title: Custom-table publication requires validation configuration
product_area: platform
module: queries
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Custom-table analysis, preview, publication and revalidation require the configured validation
  workspace, which the recorded production configuration deliberately omits.
constrains:
  - DOM-PFM-QRY-001
  - STATE-PFM-QRY-001
  - WF-PFM-QRY-009
  - WF-PFM-QRY-010
  - SCR-PFM-QRY-018
origin: >-
  docs/queries/custom-query-tables/rhythm-custom-query-tables-architecture.md (phase 1 accepted
  2026-10-12); FND-PFM-QRY-042
alternatives:
  - option: Validate against a customer workspace
    why_not: That would expose customer rows through staff authoring without the required access model.
consequences:
  - Production cannot publish a new custom query table under the pinned configuration.
  - The production revalidation pass has no configured validation workspace to use.
supersedes: []
evidence:
  - 'services-platform at ad3f6a6: modules/queries/services/custom-tables/validation-tenant.ts'
---

# Custom-table publication requires validation configuration

## Context

Custom SQL needs a controlled place for validation. The current architecture does not grant staff access to customer records for this purpose.

## Decision

Custom-table analysis, preview, publication and revalidation require the configured validation workspace, which the recorded production configuration deliberately omits.

## Alternatives Considered

Validate against a customer workspace: That would expose customer rows through staff authoring without the required access model.

## Consequences

Production cannot publish a new custom query table under the pinned configuration. The production revalidation pass has no configured validation workspace to use.