Learn · Running an organization · 2 min read
Templates
By the third RFP response, the third client onboarding, the third product launch, your team knows how this kind of work goes. Templates turn that knowledge into a starting point.
A template is a space
There's no separate template editor to learn. You build a real space the way your process actually works — labels and completion states, completion prompts, milestones, cycles, saved views, perhaps example items and starter documents. Then, in Space Settings: Publish as Template.
You choose what the template carries:
- The structure always travels: labels, values, colors, completion states and prompts, milestones, cycle configuration, saved views.
- Items are optional — include them as worked examples ("here's what a filled-in space looks like") or publish structure only.
- Documents are optional too: starter briefs, checklists, your decision- record format.
- Comments on included items become read-only sample discussion.
Dates that shift
A template stores its dates relative to a reference date. When someone creates a space from it and picks a start date, every milestone deadline and item date shifts accordingly. The template's "demo day, week 6" becomes your week 6.
Using and managing templates
Creating a space starts from a template — pick one, name the space, pick a start date, done. The new space is your own fresh copy: rename the labels, drop the milestones, change everything. The template got you started; you own what happens next. No admin-locked workflows — the people doing the work can adapt the process to reality.
Organization admins see all published templates under Settings → Organization Templates — rename, delete, keep the library tidy. Updating one is republishing from its source space.
(Smaller-scale reuse — a meeting-notes format, a decision-record skeleton — wants a document template instead.)