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

Answer

Likely explanation: A linked database view is a reference to the same underlying rows; editing any property in one view updates the source record, and that change is instantly visible in all other linked views and through the Notion API. A synced block, however, mirrors only the block‑level content (text, images, etc.) and does not preserve database row identity, relations, or property schemas; edits to the block content propagate bidirectionally, but the API treats the block as a separate object, not as a database row.

Confirmed facts:

• Linked views inherit permissions from the source database; a user who cannot edit the source cannot edit the view.
• Synced blocks enforce permissions per containing page; a user must have access to both the source block and the page where the block is synced to see or edit it.
• The Notion API returns the same record ID and current property values for a row regardless of which linked view is queried, guaranteeing API‑level consistency.
• Synced block content is accessible via the block API, but there is no notion of a "row ID" or relation link that survives across pages.

Steps to achieve near‑instant API‑visible cross‑page updates

1. Create a source database that holds the status table and its instructions.
2. On each project page, use "/link" to create a linked database view of that source database.
3. Keep the view in "sync" mode (default) so any property edit propagates immediately to the source and thus to all other views.
4. To verify via the API, query the source database (or any linked view) for the record ID before and after an edit; the ID remains unchanged and the updated property values appear in the response.
5. If you need only prose or instructions (no structured rows), place that content in a synced block instead; edits will appear everywhere the block is synced, but you must use the block API to read it, and no database‑level relations are preserved.