Publish organisation knowledge

Prepare and publish shared guidance

Knowledge is owned by your organisation, rather than a legacy workspace.

1. A team administrator appoints a Knowledge Editor or Publisher through knowledge assignments.
2. An editor prepares the guideline, strategy, standard or risk/privacy template as text.
3. An explicitly appointed publisher releases a version.
4. Organisation members with governance access can read that published snapshot and reference it in project submissions.

Working drafts are not shared through publication reads. Published versions are immutable: revise the draft and publish a new version instead of editing history.

Team administration alone does not grant curation or publication authority. Knowledge assignments do not grant project or architecture-board access.

The pilot retains plain text and optional reference links. It is not a private document-upload repository.

Find earlier architecture decisions

Open Decision library to search your organisation's published historical decision records. Filter by keywords, domain, recorded outcome or decision date. Enable the history filter to include earlier, deprecated and retired publications. Read the rationale, applicability and conditions before using a record as a precedent. An earlier approval does not approve your project and cannot replace the current guidance required for submission.

Knowledge Editors can record an existing decision with its original source reference and context. A Publisher must release the organisation-visible version before it appears in search. This is publication of a historical record, not a formal decision issued by Xyreka. Private drafts, board discussion and retained legacy decisions are not automatically searchable.