Skip to main content

Creating and publishing farm documents

Written by Sven Poppelmann

Author farm documents in the web editor, then publish a PDF record when they are ready. Open Records > Evidence and choose the Documents type chip to find uploaded and authored documents. Documents is no longer a separate Records tab or sidebar destination.

Creating and editing

  1. Open Records and choose Upload > New Document.

  2. Enter the title and choose the scope and category. Set any responsible person or review date offered.

  3. Choose an available template if useful, then click Create Document.

  4. Edit the content and details. Auto-save is scheduled after five seconds without changes; Ctrl+S or Cmd+S also requests a save.

  5. Check the saved state. A timer or shortcut does not guarantee that a network save succeeded.

Review and publication

Use AI Review for suggested feedback where offered. Have the responsible person review site-specific and regulated content rather than relying on an AI status.

Click Publish when ready and wait for confirmation. Successful publication renders a PDF, stores it in the vault and updates publication and version metadata. Check the published output before sharing it.

Viewing and sharing

Open the document viewer to read it. Use its PDF button, or the Records document card's Download PDF, and check the downloaded output before sharing it with appropriate recipients. Do not rely on the authored-document viewer's Share button to create a working link; that button is not connected to a sharing action in the current interface.

A review date records when a document should be checked; do not assume it guarantees a reminder. Later edits should be reviewed and published as appropriate rather than assuming every edit automatically creates a new published version.

Share from the editor

After successfully publishing the document into the vault, return to its editor and use Share > Create Share Link where permitted. Check the result and copied link. Existing links can be copied from the editor's dialog. This working editor flow is distinct from the unwired viewer Share button above. The generated link is public to anyone holding it, not a recipient-specific farm-access grant; share it only when that access is appropriate.

Did this answer your question?