Ngenaire Docs
Log inSign up free

Document Templates

A document template is a reusable skeleton — sections, variable slots, and supported export formats — that your organization uses to author and generate consistent documents. The Document Templates page is an organization-wide library: everyone in your org sees the same set, so a template authored once is reusable across every project.

Location: /system-definition/document-templates (sidebar: Define → Document Templates).

Document Templates vs. Report Templates

These are two distinct things — don't confuse them:

  • Document Templates (this page) — an org-wide library of reusable document structures (a Requirements Specification skeleton, a Test Plan outline, …) that you browse, create, and version here.
  • Report Templates — used by the AI Report Builder to control the layout and styling of generated reports. See Report Templates.

If you're trying to change how a generated report looks, you want Report Templates, not this page.

What a template defines

  • Name and description — what the template is for.
  • Document type — e.g. Requirements Specification, Test Plan, Architecture Description; used for filtering.
  • Format — the authoring/export format(s) the template supports.
  • Status — e.g. draft or active.
  • Versions — each template can carry multiple versions so it can evolve without disturbing documents authored against an earlier one.
  • Variables and mappings — declared slots the template fills in (e.g. {{system_name}}), optionally mapped to a Ngenaire field so they populate automatically.

Common actions

  1. Browse and filter. Narrow the library by search query, document type, format, or status.
  2. Create. Add a new template to the org library.
  3. Version. Create a new version of a template as it evolves; earlier versions stay available for documents already authored against them.
  4. Edit. Update a template's structure, variables, and mappings.

Permissions

  • Organization admins can create, edit, and version templates.
  • Members see the library read-only.

Tips

  • Name templates after the artifact, not the project. NASA-7150 Requirements Spec is reusable everywhere; Project-X SRS is not.
  • Use variables generously. Anything that varies between documents — system name, review date, customer — belongs as a variable.
  • Version deliberately. A new version lets new documents pick up the change while older documents stay pinned for review.

Related