Linked database view or synced block for cross-page updates with API visibility

A design needs a single source for a status table and accompanying instructions that appears on multiple project pages. The requirement is near-instant visibility of edits in the web client and consistent read access via the Notion API for downstream automation.

Linked database views present filtered views of one source database, with edits to properties mutating the same rows everywhere in the UI. Permissions are inherited from the source database. Synced blocks mirror block content bidirectionally between pages and provide a single source for prose or templates, but they do not sync structured rows, properties, or relations. Permissions for synced blocks are evaluated per containing page. Formulas are evaluated client-side in the UI and are not materialized as queryable properties for API database queries.

What is the propagation behavior for property edits made in a linked database view versus content edits in a synced block when API consistency is required? Does a synced block preserve database row identity and relation links across pages, or only block-level content? How do page-level permissions on a synced block interact with database-level permissions on a linked view for the same workspace?