---
id: SCR-PFM-QRY-014
title: Data export settings
route: '/console/{tenantId}/dataManagement/dataExportSettings'
surface: console
product_area: platform
module: queries
revision: 1
status: draft
design_intent: proposed
implementation_evidence: observed
inference: []
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
purpose: >-
  Configure workspace package choices, notification recipients and storage destinations through the
  existing settings screen.
supports:
  - JNY-PFM-QRY-006
  - CAP-PFM-QRY-018
permission: platform.data-exports.read to view; platform.data-exports.manage to change
entry_from:
  - Data export history
  - Data management navigation
exits_to:
  - Data export history
displays:
  - field: >-
      Package flags, retention, notification people, eligibility and destinations in the console
      settings model.
    source: getDataExportDefinition
  - field: Storage-connection choices requested through the console adapter’s undeclared picker route.
    source: Integrations connections (owned by MOD-PFM-INT)
actions:
  - label: Save settings
    operation_id: saveDataExportDefinition
    permission: platform.data-exports.manage
    confirm: false
  - label: Add Destination
    operation_id: addDataExportDestination
    permission: platform.data-exports.manage
    confirm: false
  - label: 'Enable, disable or change path'
    operation_id: updateDataExportDestination
    permission: platform.data-exports.manage
    confirm: false
  - label: Remove destination
    operation_id: removeDataExportDestination
    permission: platform.data-exports.manage
    confirm: true
states:
  - settings loading
  - initial defaults
  - settings cannot be edited
  - workspace eligibility refusal
  - version refusal or conflict
  - settings envelope mismatch
validation:
  - BR-CAP-PFM-QRY-018-03
  - BR-CAP-PFM-QRY-018-04
  - BR-CAP-PFM-QRY-018-05
  - BR-CAP-PFM-QRY-018-12
patterns:
  - Full layout (PageLayout default)
  - 'settings cards (package, destinations, notifications, schedule)'
  - add destination dialog
component: >-
  components/data-management/data-exports/data-export-settings-screen.tsx, destinations-card.tsx,
  package-card.tsx, notifications-card.tsx, schedule-card.tsx, add-destination-dialog.tsx
evidence:
  - >-
    react-console at baf6dae:
    app/(console)/console/[tenantId]/dataManagement/dataExportSettings/page.tsx;
    components/data-management/data-exports/*-card.tsx
controls: [TC-AVL-004, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-AZ-005, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-DAT-004, TC-DAT-005, TC-IAM-001, TC-IAM-002, TC-IAM-003, TC-IAM-004, TC-IAM-005, TC-IAM-006, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-004, TC-LOG-005, TC-MON-001, TC-PI-001, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005, TC-PRV-001, TC-PRV-002, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-VEN-001, TC-VEN-002, TC-VEN-003]
---

# Data export settings

## What the Screen Is For

Configure workspace package choices, notification recipients and storage destinations through the existing settings screen.

## What It Shows and Lets People Do

The page shows package, destination, notification and recurrence cards. The adapter’s settings envelope, missing write version and undeclared schedule and picker routes differ from the pinned service, so recurrence and live editing remain unproven integration paths.

## States and Errors

Read permission does not imply modification permission. Eligibility refusal prevents customer settings writes, and the service’s version requirement is not supplied by the current settings adapter.

## Patterns It Must Respect

The full-width settings layout uses cards and destination dialogs. The recurrence card is an observed console component whose service route integration remains a finding.