Editor and publisher

No. The News page uses fictional examples to show decisions, construction progress and practical arrangements. Read the demo labels. A document marked “Demo: no file” is a placeholder, not a downloadable client document. The certificate example is also fictional and awards no qualification. Use these screens to discuss whether information is clear: what changed, whom it affects and what action is needed. For actual dates, documents and arrangements, use the confirmed channel for your own project.

• /experience/app/nieuws

No, the Deploy demo does not save real decisions or approve anything. A displayed decision or completed worksheet does not replace authorised approval. Use your project's agreed decision record for real work. A future process must preserve the proposal, evidence, decision-maker, reasoning, conditions and effective date, and connect the decision to reviewed information for its audience. Before use, test approval permissions, corrections and publication with separate roles. Keep drafts visibly distinct from approved decisions.

Yes, publishing in Codex follows draft, review, approval and publication. Administrators add or replace handouts at /manage/handouts: one file at a time, up to 20 MB. They manage sessions at /manage/sessions and view operational status at /manage/operations. This does not make the fictional Deploy news page a working project publication process: nothing is actually saved or approved there. Keep the source, owner, audience, language and effective date with real content. Do not place confidential client information in the demo.

• /experience/app/nieuws

Gather what changed, who is affected, what it means and what action is needed. Check the source and whether information is planned, in progress or confirmed. Record the location or audience, owner, effective date and review date. A photograph or layout cannot replace those facts. Identify open decisions. Codex publication follows draft, review, approval and publication. Deploy project news remains fictional and is not actually saved or approved. Prepare real project information in the agreed secure environment.

Each translation is linked to one source version. After a source change, the translation must be reviewed again. Publishing follows draft, review, approval and publication. During review, check both languages, instructions, links and associated files. The language control changes only the website and does not prove that a file is an up-to-date translation. The role materials are dated 4 October 2026.

No. Support contains guidance on using the Codex, including role manuals, role presentations and practical help. Role files are publicly downloadable, except the Dutch consultant manual, which is not yet available. Workshop files W01 through W16 require sign-in and download permission. Approved strategy activity materials belong with method pages. Internal audit documents and source files are never public. One library therefore does not mean that all content shares the same destination or access rules.

After approval and publication. Role manuals and presentations are already available without signing in through the role pages. The Dutch consultant manual is not yet available. Each download button shows format, language and file size. The materials are dated 4 October 2026 and were released by the owner without a virus scan. Automatic virus scanning is not yet available. Publication therefore does not mean that a file has been automatically scanned for viruses.

Administrators replace a handout at /manage/handouts, one file at a time, with a maximum of 20 MB. Publishing follows draft, review, approval and publication. Check the other language too: a changed source requires another review of its linked translation. Report a FAQ correction through your Workplaced contact, including the page, language and incorrect text. There are no email notifications for new or changed content.