Platform Updates

Partners Dashboard V2 now closes an unfinished social-account connection when the operator changes client scope. Only the original connection window can complete that attempt, so a late browser message cannot refresh another client’s workspace. Local browser checks exercised matching, unrelated, and scope-change completion paths without contacting a social provider or creating an account connection.

Finance automation now keeps its delivery-route list, event scopes, and linked account choices in the same active partner view during a refresh. A delayed request from a previous partner scope is ignored, so operators do not see a mixed set of notification routes while changing scope. Local browser checks covered route filtering and selected-route detail without contacting a delivery provider or changing a destination.

The EMS event creation and event-details workspaces now reset when an operator changes active partner scope. Pending work from the previous partner cannot remain on screen as an actionable event form or event record. Local type checks passed; no event, image, registration setting, or hosted record was changed.

Event-detail reads and saves now also apply only while their original scope is mounted, preventing a late prior-scope result from replacing the active event screen or refreshing the dashboard session.

Shop Configuration now also resets its retained catalog and settings workspace when partner, user, or permissions change, keeping edits within the active authorized event scope.

Partners Dashboard V2 now includes the required publication-governance details when operators author a survey: its purpose, data classification, retention, disposition, accountable owner, and respondent privacy notice. Survey drafts remain editable as before, and older drafts gain these fields only when an operator chooses to add them. Local contract, type, and authenticated browser checks passed with temporary data cleanup; no hosted survey or deployment was created.

Partners Dashboard V2 now restores the Shared Data and Finance dimension-policy workspaces from the earlier dashboard. Authorized operators can review scoped parties, places, dimensions, and Finance policies, then create candidate records through the existing receipt-backed service. Finance handoff posting and owner records remain in their respective Finance and Asset workspaces. Local type and authenticated browser checks passed; no hosted records were changed.

The Linked Operations timeline also restores scoped owner-record search, so operators can find an authorized cross-system record and open its authoritative workspace without copying it into V2.

Linked Operations links from EMS, EPS, Finance, and Asset Management now retain their selected section, and cross-system search results open the corresponding V2 workspace.

Contextual EMS, EPS, Finance, and Asset links now retain the requested system, record type, record ID, or event context after arrival in Linked Operations.

Partners Dashboard V2 now lets authorized operators record supported integrity exception actions and reviewed-link decisions from their scoped rows. Every command carries the rendered record revision, a required reason, and a new idempotency key; the existing service remains responsible for authorization, state transitions, and receipts. Local command-contract, type, and browser checks passed with fixture data only. No hosted record was changed.

Partners Dashboard V2 now also lets authorized operators propose a reviewed cross-system link by naming both existing owner records and their allowlisted relationship. The service reloads both records, verifies partner scope, and keeps the proposal pending independent review. Local type, command-contract, and browser-dialog checks passed; no hosted link was created.

Partners Dashboard V2 now lets authorized operators create an event asset deployment request with its event, optional plan, timing, and shared-place context. Asset Management still owns the manifest and movement lifecycle. Local type and browser checks passed; no hosted deployment was created.

Partners Dashboard V2 now also lets authorized operators advance a scoped event deployment through supported lifecycle steps with a revision and recorded reason. The Worker continues to enforce state, access, and receipt rules. Local browser, contract, and type checks passed; no hosted deployment changed.

Partners Dashboard V2 now lets authorized operators approve or archive shared parties, places, and accounting dimensions with a recorded reason and revision. Local type, contract, and browser checks passed; no hosted identity changed.

Partners Dashboard V2 now lets authorized Finance operators approve or reject a candidate dimension policy with a recorded reason and revision. The existing service continues to enforce policy scope and receipts. Local type, contract, and browser checks passed; no hosted policy changed.

Partners Dashboard V2 now also shows scoped AssetManage-to-Finance cost handoffs and posting batches in Linked Operations. The underlying owner records remain managed in Finance and Asset Management. Local type checking passed; no hosted financial record changed.

Partners Dashboard V2 now lets authorized Finance operators record the supported cost-handoff decisions from Linked Operations: approve, settle, partially settle, reject, cancel, reverse, or correct. Each action uses the current record revision, a settlement amount where relevant, and a required reason. Posting batches can also be reconciled from their linked row. The existing Finance and Asset Management services still validate authority, state, recent verification where required, and receipts. Local type, contract, and browser checks passed with fixture data only; no hosted financial record was changed.

Partners Dashboard V2 now restores the controlled Finance entry points for AssetManage cost handoffs and posting batches. Authorized operators select an existing AssetManage source or journal batch and provide the required Finance context; the service reloads the source, verifies scope and source integrity, and keeps the linked records and receipts in their owning systems. Local type, contract, and browser checks passed with fixture data only; no hosted financial record was changed.

Partners Dashboard V2 now restores EMS-to-FinManage accounting coding proposals in Linked Operations. Authorized operators can create a proposal from an existing EMS accounting source and its linked Finance journal, then an independent Finance reviewer can accept, reject, request a replacement, mark it stale, or correct it. The service derives the proposed coding from the authoritative EMS source and records the governed decision. Local type, contract, and browser checks passed with fixture data only; no hosted accounting record was changed.

Partners Dashboard V2 now lets authorized operators create and review shared identity crosswalks in Linked Operations. Parties, places, and accounting dimensions can be linked to their allowed owner records, then independently approved, rejected, or superseded. The service reloads the owner record and continues to enforce partner scope, permissions, source integrity, and required recent verification. Local type, contract, and browser checks passed with fixture data only; no hosted identity or crosswalk changed.

Partners Dashboard V2 now restores EPS-to-FinManage procurement requests in Linked Operations. Authorized planners can create a Finance request from an existing requirement or work item, including quantities, dates, dimensions, and commercial estimates, and can cancel a linked request with a recorded reason. The service continues to validate the planning source, partner scope, and Finance authority. Local type, contract, and browser checks passed with fixture data only; no hosted procurement record was changed.

Partners Dashboard V2 now restores Finance-to-AssetManage goods-receipt intake in Linked Operations. Authorized operators can create an intake from a Finance goods receipt line, then record acceptance, quarantine, rejection, return, or correction quantities with the required inspection reason and correction lineage. Local type, contract, and browser checks passed with fixture data only; no hosted receipt or asset record was changed.

Partners Dashboard V2 now sends the correct AssetManage return-start lifecycle transition for event deployments and also exposes the existing request, reconciliation, and exception transitions. Local type and contract checks passed; no hosted deployment changed.

Partners V2 now records the full asset-deployment workflow: custody handoffs and movements, returns, condition problems, substitution proposals and reviews, reconciliation, and evidence-backed exception approval. Teams using event asset operations can enter the manifest item, movement, replacement, and evidence information required for each action. Local fixture browser and contract checks covered the restored controls.

Partners V2 now provides the event-scoped EMS-to-FinManage reconciliation view. It shows linked source totals, digest drift, close blockers, and the current accounting annotation, with the Finance review action available when needed. Local fixture browser and contract checks covered the restored workflow.

Partners V2 now supports the complete controlled exception workflow: assignment, snoozing, evidence-backed approvals, retries, and the approved owner-system fix when one is bound to the exception. The action form collects the fields each workflow requires and shows fix execution only after its preview is available. Local fixture browser, contract, and type checks passed.

Partners V2 now supports superseding, unlinking, and relinking a reviewed cross-system record. A relink collects the replacement owner system, record, and relationship before the server validates that it is permitted and belongs to the current partner. Local fixture browser and contract checks covered the flow.