'Organization users' can view all org notes.
Org notes are hidden to guests.
Org notes are available with 'Pro' (and above) subscriptions.


'Org notes' are a place to record best practices and lessons learnt from earlier projects and positioning this at in the right place on all existing and future projects. 


When an org note is entered against an article/ clause/ section/ system it is automatically displayed against every instance of those items across all projects and masters, existing and future, organization-wide.


This means that when you enter an org note against an item, for example against UK - CAWS section F10 Brick/ block walling, wherever your teams see this section in their projects (or masters) they will see the presence of the org note. So, when they add F10 to a new spec, whether they add it from the content set, or copy from the masters or an earlier project, they can see and review the org note.


Like masters, org notes are confined to the organization and not displayed to guests. So, org notes are not copied as part of copying specs between organizations.


There are three places where org notes are displayed.

  1. In the specification editor, to show the presence of 'Org notes', a yellow count is displayed to the left of the article/ clause.

  2. Clicking on the yellow icon opens the 'Org note' panel and displays the corresponding note.

  3. The platform will display the org note in the Org note table.


The platform will display the org note in two locations (in the editor and 'Org notes' area) to all organization users across all your organization’s projects and masters, existing and future.


Animation showing where org notes are displayed in Chorus