Templates workspace
Card Types define abstract classifications and constraints. Templates define the properties, relationships, content sections, and creation-form fields available in concrete cards. Each has an independent selection, so editing one does not replace the other.
Four tabs
- Entity Templates: characters, locations, organizations, and other entities.
- Event Templates: events and fields such as dates, participants, and locations.
- Relation Templates: entry points for relationship-related templates.
- Writing Templates: text files with a prepared structure.
The right-side Schema panel contains Card Types, Properties, and Relationships. It defines which structures may be used; the main Entity or Event template determines which fields a concrete card actually displays.
Structure sources
| Source | Scope | Behavior |
|---|---|---|
| Defaults | Every Project | Factory definitions supplied with Scroll; select the Pencil button to save a Global customization |
| Global | Projects used by the current account on this device | Reusable definitions for more than one Project |
| Project | Current Project | Definitions that apply only to the current Project |
Each ID appears once as its effective row. Its source badge reads Default, Customized globally, Global custom, Customized for this Project, or Project custom. If an upstream version changes or is no longer available, Scroll shows a diagnostic without discarding saved content.
Editor
Selecting a row only previews it; select its Pencil button to edit. Properties and relationships use compact summary rows, with only one expanded at a time. You can edit display names, choices, relationships, content sections, and creation-form order. IDs, types, and directions that would reinterpret existing data are locked after saving.
- Free can edit a Default and save or reset its Global customization.
- Plus can create, duplicate, import, and manage Global definitions.
- Pro can additionally create or override Project definitions and migrate existing managed folders.
The first time a Global custom definition is used in a Project, Scroll may ask you to establish that Project's folder binding with the system folder picker. Paths cannot be typed manually, and a Template folder must be a direct child of its Card Type root.
See Customize a Project model for modeling, dependency checks, and migration steps.