LINA comes with five sample processes. Find them at the top of the template list in the designer, marked Bundled. You can View them and Copy them; the copy is your own template, which you finish and publish.
| Sample | Use it for | What it shows | After Copy |
|---|---|---|---|
| Document lifecycle | policies, guidelines: review, approval, yearly revision, retirement | the whole cycle with document states and a due date | choose the Jira project and issue type of the two tickets |
| Procedure with proofreading | handbooks, procedures that need a language check before approval | a subprocess with its own ticket | the subprocess Proofreading is copied too: choose the project and issue type in it, publish it first, then the procedure |
| New procedures start by themselves | every new page under a parent page gets the review without a click | a start rule with a label condition | select Start, choose the Space and Parent page; choose the project and issue type of the tickets |
| Specification to Jira work | specifications, change requests: approval creates the work | the approval creates the implementation ticket and the document waits until it is done | choose the project and issue type of the ticket |
| Decision record | decisions, ADRs, meeting decisions — no Jira needed | a decision stays in force until it is marked superseded | nothing — publish it as it is |
Then Save and Publish. If something is missing, publishing tells you what (Publishing checks).
Change anything you like in the copy: names of figures and states, texts of tickets, due dates, who may start it. The samples themselves never change and never run.
Draft (the author clicks Continue) → a required review ticket → Review → Approve?: Approve or Reject with a comment (back to Draft) → Approved for 365 days → a required revision ticket → Expired → Keep the document?: Revise (back to Draft) or Retire with a comment.
States: Draft, In review, Approved, Revision due (valid), Retired (not valid — readers see the banner This document is no longer valid).
Draft → subprocess Proofreading (a required ticket “Proofread …”; over when it is done) → Approve?: Approve (ends as Approved) or Return with a comment (back to Draft).
While the editor works, the badge shows LINA · Proofread · Proofreading › Proofread. When the ticket is done, the procedure moves on by itself.
States: Draft, In proofreading, Proofread, Approved.
Starts on every new page created under the parent page you choose, if the page has the label procedure. A required review ticket is created at once → Review → Approve?: Approve (ends as Published) or Return with a comment → Rework (the author clicks Continue) → a new review ticket → Review again.
Pages that get the label later, or are moved under the parent, do not start it — that is intended. To use other labels, edit the condition at Start.
States: In review, Rework, Published.
Draft (the author clicks Continue) → Approve?: Approve creates the ticket “Implement …” in Jira, or Return with a comment → Implementation waits until the ticket is done → ends as Delivered.
The ticket’s Source document panel tells the implementer which specification it comes from. Add more Create ticket actions to the Approve line if one specification means several tickets.
States: Draft, In implementation, Delivered.
Proposal (the author clicks Continue when it is ready) → Decide: Accept (state Decided, a note is written as a comment on the page) or Reject with a reason (ends as Rejected) → In force until someone chooses Mark as superseded with a reason (ends as Superseded).
Superseded and Rejected are in the group Not valid, so readers see the banner and search can tell valid decisions from old ones.
To e-mail people when a decision is accepted, select the Accept line, open the Decision note action and choose people under Mention.
The Document lifecycle sample, step by step:
procedure.More in Start a process automatically.
The document waits for the ticket of a colleague who has left.
A space admin (or someone named in the space settings) opens the page, clicks Continue anyway…, writes the reason — “Reviewer left the company, review done by J. Smith in the meeting on 3 March” — and confirms. The history keeps the name and reason. See Continue anyway.