Administrators configure and inspect the foundation for workspace packages. The examples distinguish accepted settings and queued history from later package completion, and retain the unfinished actions as explicit limits.
Package powers do not disclose another person’s query file. The combined example crosses the feature boundary through file access or workspace cleanup; those capabilities remain owned by their existing features. The lifecycle and regression examples revisit retained state after a later change rather than repeating individual rule rows.
A live nonsandbox workspace has an administrator and an available destination connection.
Steps
Save settings, add a destination, request an export and inspect its queued history and package actions.
Expected
Admission snapshots the settings; unfinished generation and delivery actions state their current limits.
Data
Use an isolated workspace, named fixture records and the caller grants described by the prerequisites.
Source
services-platform:modules/data-exports/tests/integration/services/persistence/definitions.integration.spec.js#refuses a second definition for a tenant, leaving one,services-platform:modules/data-exports/tests/integration/services/persistence/destinations.integration.spec.js#refuses a sixth destination, leaving five,services-platform:modules/data-exports/tests/integration/services/persistence/executions.integration.spec.js#answers it queued, at the request’s instant, with the definition’s switches copied and the allowance counted,services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#is answered 404 for the manifest of an execution with no package yet
02Package powers do not disclose another person’s query fileinteractionproposed
An export administrator lacks query-file ownership or schedule-management authority.
Steps
Request another person’s query file with only package powers, then inspect a permitted workspace execution.
Expected
The query file remains concealed while the permitted workspace execution is readable.
Data
Use an isolated workspace, named fixture records and the caller grants described by the prerequisites.
Source
services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#is refused every read route when it holds the other three keys and the administrator tier,services-platform:modules/queries/tests/integration/services/exports/query-export-routes.integration.spec.js#answers the requester their export
03Workspace removal clears retained export and snapshot historylifecycleproposed
An isolated workspace has queued package history, monthly versions and indexed records.
Steps
Delete it, let open rebuild work settle and complete participant cleanup.
Expected
All three inventories reach zero only for the deleted workspace; a surviving control retains its resources.
Data
Use an isolated workspace, named fixture records and the caller grants described by the prerequisites.
Source
services-platform:modules/data-exports/tests/integration/services/persistence/executions.integration.spec.js#answers it queued, at the request’s instant, with the definition’s switches copied and the allowance counted,services-platform:modules/snapshots/tests/integration/lifecycle/pipeline/snapshot-pipeline.integration.spec.js#removes every snapshot row, run and override of the purged tenants, the run's version chain included,services-platform:modules/quick-search/tests/integration/services/maintenance/tenant-participant.integration.spec.js#purges the tenant once the rebuild has settled, the job’s own three tables included
04Export authority remains separate across customer and staff surfacespermissionproposed
An administrator, a Power User and support staff have their respective scoped grants.
Steps
Read settings, request immediate work and inspect history through customer and HQ surfaces as each caller.
Expected
Only the route-specific customer authority admits work; staff use their permitted HQ reads and customer roles do not enter HQ.
Data
Use an isolated workspace, named fixture records and the caller grants described by the prerequisites.
Source
services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#is refused every read route when it holds the other three keys and the administrator tier,services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#is refused every console route, whatever it holds at platform scope (rule S1)
05A first queued request keeps its single active slotregressionnegativeproposed
The generation dispatcher remains unavailable and one export request is queued.
Steps
Repeat Export now, request cancellation and reopen history.
Expected
The repeat conflicts, cancellation reports not implemented and history retains the first queued request rather than claiming recovery.
Data
Use an isolated workspace, named fixture records and the caller grants described by the prerequisites.
Source
services-platform:modules/data-exports/tests/integration/services/persistence/executions.integration.spec.js#answers it queued, at the request’s instant, with the definition’s switches copied and the allowance counted,services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#is answered 404 for the manifest of an execution with no package yet,services-platform:modules/data-exports/tests/e2e/data-exports.e2e.spec.js#exports now: 202 with the execution queued