Templates
You rarely need to write an instruction from nothing. The gallery holds starting points that you copy, change and make your own.
Three ways to begin
- Describe it. Choose "Describe it and I", say which tickets it is about and what you want done, and it reads your real tickets to write a first draft. Nothing is created until you review and save it.
- Start from a template. Pick one from the gallery and the editor opens pre-filled.
- Start from scratch. Choose Instructions for a shell-based instruction or Microsoft 365 for a workflow.
A fourth source is Autosight, which finds recurring problems in your history and drafts an instruction for the ones worth automating.
What the gallery holds
There are seven templates in three groups.
| Group | Templates |
|---|---|
| Patching and updates | Windows patch installation failure; Server reboot pending after patching; macOS patch installation failure |
| Databases | SQL Server: transaction log, backup failure, service down |
| Microsoft 365 | Onboard New Employee; Reset User Password; Remove User from Group |
The patching and database templates are written as instructions and are long on purpose: they spell out the situations a real fleet produces. The Microsoft 365 ones are short fixed workflows with fields you fill in each time.
Copies, versions and history
Choosing a template never changes the template and never runs anything. The editor fills in a copy, and nothing is saved or switched on until you review it and save.
A copy remembers which template and which version it came from. If the template is improved later, your copy shows an update banner. Applying the update is an edit like any other: you review it and save it.
Every edit to an instruction is kept in its History tab with who made it and when, and you can restore an earlier version in one click. The other tabs of the editor are Settings, Security, Scope, Resolved tickets, History.
Limiting where it applies
The Scope tab narrows an instruction to servers only, PCs only, or all endpoints, and can limit it to chosen companies. An instruction also only ever matches machines of the operating system it was written for.