Records Inside a Knowledge Article: A Working View or a Fixed Example?

When a knowledge article contains business records, decide whether readers are looking at current work or a fixed example. The two serve different purposes. An instruction that embeds an operational list should not imply that everyone sees the same records or that restoring old wording recreates an old business state.

This guide concerns the relationship between explanatory content and inserted data. It is not a request to publish internal records on your website. Use invented records when briefing a developer or demonstrating the feature.

Choose what belongs inside the instruction

A fictional service team might explain how to review open jobs and place a relevant job view beside the instructions. That can save navigation. A training example, however, may need a stable sample that still makes sense after real jobs close.

Choose deliberately between a link to the operational screen, an inserted view and a dated illustration. Label the purpose. A screenshot of last month's queue should not look like today's workload; a current list should not be described as the exact example used in a past training session.

Odoo 19 documents inserting a view or a link to a view from another app into a Knowledge article. That supports the possibility of connecting instructions and application data. It does not establish a particular refresh interval, offline copy or historical snapshot for your implementation.

Specify what the view means when it opens

For an operational view, agree the record population, filters, sorting and the treatment of the current user. Does “my jobs” mean the article author's work or the reader's? Which date and location apply? The page should not leave staff guessing why their lists differ.

Ask what happens when source records change while the article remains open. Specify how readers refresh, what freshness information they need and how a failed load appears. Do not present an old retained display as confirmed current work. These are requirements to demonstrate, not documented Odoo refresh guarantees.

If the view supports editing, identify that separately from reading the instructions. Changing a record is an operational action, not a change to the article's wording. Make the route back and the action's consequences understandable.

Page access and data access are separate

Odoo explicitly says that users without access to an inserted view cannot see it in Knowledge even if they can access the article. Its web-sharing note likewise says that possession of the article URL does not reveal inserted content without the relevant access.

Do not treat a visible article as proof that the reader can use every example in it. Conversely, do not solve a missing view by granting everyone broader data access. Provide useful instructions or an authorised sample for people who should not see the operational records.

Test the chosen access rules with harmless accounts at both layers. Include the embedded display, its linked destination and any available export. A successful page load alone proves neither complete access nor secure denial.

Restoring text does not prove that data went back in time

Odoo documents restoring a previous article version. The cited instructions do not establish that this also restores the source records displayed by an inserted view. Keep those two claims separate.

If your team must preserve what a reviewer saw, define a deliberate dated snapshot with its scope and access policy. Do not assume article version history is an operational audit archive. Equally, a frozen training sample should not need access to live customer records merely to remain understandable.

Accept two readers and a changed record

Use a synthetic job and two test readers in the acceptance criteria. Give one reader the agreed source-data access and the other article-only access. Compare the instructions, inserted view and linked destination. Change the synthetic job, then exercise the agreed refresh path and unavailable-data state.

Restore an earlier text version and check what actually happens to the inserted data without assuming a rollback. Verify that a dated example stays recognisable as an example. Bring these decisions to an internal-app discussion. The useful deliverable is a clear connection between instructions and work, with honest limits on freshness, history and visibility.

Source

Odoo 19: Knowledge, read 26 October 2026. View insertion, the separate access boundary and article-version restoration are documentation-based. Refresh rules, snapshots and proposed tests above are specification guidance, not independently verified product behaviour.