Schema & fields
Studio is schema-first: you design your types and their fields before you create a single row. A file is bound to one schema type at creation, so getting the shape right up front saves you from reshuffling files later.
Field type reference
Studio schemas support these field types:
| Type | Renders as | Notes |
|---|---|---|
text | single-line input | |
richtext | Monaco Markdown editor with live preview | Multi-line formatted text |
number | numeric input | Sub-format: Decimal / Integer / Percent |
currency | numeric input with currency code | 18 ISO currency codes to choose from |
date | date picker | |
datetime | date + time picker | |
checkbox | toggle | true/false |
select | single-choice dropdown | You define the option list |
multiselect | multi-choice | Same option list mechanism as select |
url / email / phone | validated single-line input | |
image |
upload + thumbnail | Stored as a graxeon-asset:// reference, not inline. Supports "automated fields" — Width and Height are computed instantly; Description and Tags are filled in later by the enrichment worker. |
video | upload + player | |
pdf |
upload | Same automated-fields mechanism as image — a Summary is computed instantly; Description and Tags are filled in later by enrichment. |
markdown | upload of a .md file | |
file | generic upload | |
relation |
picker constrained to one schema type | For a single typed reference (e.g. "Owner" on a Task, pointing only at Person). For open-ended, many-to-many connections, use links instead of a relation field. |
Adding a field with "Include automated fields" checked (
image/pdf
only) appends read-only companion columns automatically — you don't hand-create those.
Designing the schema
- Toolbar → Edit schema. This opens a two-pane editor: a left list of every Schema (type) and Relationship Type in the collection, and a right pane for whichever one is selected.
- Click + next to "Schemas" → name the type (e.g.
Company). - + Add field for each column: name it, pick a type, set sub-options
(format, currency, option list, target schema for
relation), mark required if it must always be filled. - Drag fields by the handle (☰) on the left of each row to reorder — this order is exactly the column order in the grid, so put the fields people scan first (name, status, owner) before the ones they don't (internal notes, IDs).
- Save schema.
- Repeat for every type you need. Do this before creating files — a file is bound to one schema type at creation.
- Optionally define Relationship Types here too (same left sidebar, "+" next to "Relationship Types") — gives a link a name that shows up in the picker instead of typing a custom one every time, and can optionally restrict which types it connects (From type / To type).