A Guideline in Enlivy is a structured, reusable document designed to provide best practices, internal procedures, or specific instructions related to various entities within the platform, such as invoices, bank accounts, contracts, projects, and more.
Unlike playbooks, which are step-by-step procedural walkthroughs, guidelines are strategic or instructional references.
They help teams align on standards, ensure consistency, and share internal knowledge that improves daily operations.
When to Use a Guideline
Use a guideline when:
- You want to document standards or best practices for working with a specific type of entity (e.g. how to fill in product descriptions, how to write invoice notes, how to structure contracts).
- You need a central place to share internal rules or formatting conventions.
- You want to attach helpful, non-procedural context to various modules of Enlivy.
Getting to the Guidelines Section
To add or manage guidelines:
- From the main left-side menu, go to Guidelines.
- This opens the Guideline Dashboard, where you can:
- View existing guidelines
- Add a new guideline
- Reuse, edit or delete an existing one
Guidelines Dashboard in Enlivy
Fields in a Guideline
When creating or editing a guideline, you’ll be prompted to complete the following fields:
- Title – The name of the guideline (e.g., “How to Structure a Playbook”).
- Description – A short explanation of the guideline’s purpose, audience, and what it aims to standardize.
- Target Entities – Choose where this guideline applies (e.g., Invoice, Product, Project, Playbook, Contract, Bank Account). This helps attach guidelines to the relevant modules.
- Guideline Language – Select the language or locale for the guideline (e.g., English, Romanian).
- Project (Optional) – Assign the guideline to a specific project for better organization and filtering.
- Owner – Select the person/user that owns the guideline.
- Content – A rich text editor supporting Markdown, allowing headings, paragraphs, ordered/unordered lists, and formatting for clarity and structure.
Guidelines Fields
Autosave Feature
Guidelines are automatically saved as drafts while you add or edit them. If you leave the page or get disconnected, you’ll be able to restore your latest draft the next time you return.
Prompt to restore or discard an autosaved guideline draft.
Revisions Feature
Every time a guideline is edited, a revision is saved automatically. The Revisions feature keeps a list of all changes, including:
- The user who made each revision
- The date and time of the change
You can click on any entry to open the Revisions tab, where you’ll see the full history of edits made to the guideline.
Revisions appear under the table of contents.
Clicking on a revision you can check all the details that have been change in the guideline.
Example – Adding a Guideline
The following screenshots illustrate the required fields when adding a guideline, as well as the final layout of a published guideline.
Adding a guideline – ready to be saved, fields and content have been written.
How the guideline looks in view mode.