Custom objectsTemplates
Nine shapes of real work. Each one installs a complete working type (fields, stages, default view) and then gets out of the way of your practice.
The nine, by name. Including the one our own deals run on.
- Shipped templates
- Sales deal
- Gift
- Pledge
- Membership
- Grant application
- Volunteer shift
- Case
- Program
- Program enrolment
Install a working type. Not a blank one.
A template’s value is its opinions: a grant application arrives with twelve fields, a six-stage set from research to closed, a board to work it on, and the funder as its primary relation.
- The fields the work actually needs, not a blank slate
- Stages where the work moves; none where it doesn’t
- A default view chosen for the job: board, table, calendar
- A primary relation to the person or organization it’s about
- Install it twice by mistake and you still get one type, not two
Work it like it was always yours. Because from install onward, it is.
The template opens as a board with the stages already on it. From there it is an ordinary type: your fields on top, your views saved, your spreadsheet imported into it.
- Add the fields your practice needs on top
- Rename stages, add one, retire one
- Save the views your teams actually live in
- Import the spreadsheet it replaces, mapped column by column
- Everything readable back out: CSV export and the API
Why templates work here. Three reasons worth naming.
Our deals module is one of the nine
The sales deal is a template on this same framework. We cannot neglect the machinery your grant tracker runs on without breaking our own pipeline: that is the maintenance guarantee.
Eight at once, for nonprofits
The nonprofit pack installs gifts, pledges, grants, memberships, shifts, programs, enrolments and cases in one call: a working nonprofit data model in one install.
A template is a starting point
After install it is an ordinary type. The fields, stages and views are yours to bend: the template’s job was to make the first day useful, not to have the last word.
When nothing quite fits, model your own. That’s what authoring is for.
If you’re a nonprofit, the pack: it installs eight templates in one go and you archive what you don’t use. Otherwise, install the one nearest your most painful spreadsheet and let it prove the framework.
Yes: an installed template is an ordinary type. Add fields, adjust the stage-set, change the default view. Your changes are yours; nothing snaps back.
That’s the expected case. Install the template, then run the CSV import against it: the wizard maps your columns to its fields, and the spreadsheet retires with honour.
Running the install twice produces one type, not two. It sounds small until the day two people click the same button, which is exactly the day it matters.