Creating a Resource
Step-by-step guide to defining a Resource, organizing it into Sections, and adding Fields.
A Resource is the blueprint for a type of business object - Projects, Tickets, Employees, anything your organization tracks. This guide walks through creating one from scratch and shaping its data structure with Sections and Fields.
If you haven't yet, read Resources first for the conceptual background.
Creating the Resource
Open Resource settings
Navigate to Settings → Data → Resources and select Add Resource.
Fill in the basics
- Name - the internal name of the Resource (e.g.
Projects). - Description - what this Resource is for. Helps colleagues understand its purpose at a glance.
- Alias (optional) - overrides the display name shown in navigation and headings, useful when the internal name is technical but you want friendlier wording in the UI.
- Icon (optional) - an Iconify icon name used across the UI (e.g.
lucide:folder-kanban).
Save
Once saved, the Resource appears in the Resources group of the main sidebar and gets its own item list - ready to be shaped with Sections and Fields.
Adding Sections
Sections are purely organizational groups that keep complex forms legible. They exist only on the front-end - they don't affect the underlying data model or queries.
In the Resource's settings page:
- Select Add Section.
- Give it a name (e.g.
General Details,Ticket Outcome,Financial Breakdown). - Arrange multiple Sections in whatever order suits your workflow.
Adding Fields
Fields define what data each Item captures. Open a Section and select Add Field:
| Setting | Description |
|---|---|
| Key | The machine name used in APIs and workflow expressions (e.g. target_date). Immutable after creation. |
| Label | The human-friendly name shown on forms and tables (e.g. Target Date). |
| Type | The data type - see below. |
| Required | Items cannot be saved without a value for this Field. |
| Unique | Duplicate values are rejected within this Resource (shown with a key badge). |
Choosing a type
- String - free-form text.
- Number - numeric values.
- Boolean - true/false flags.
- Date - dates and timestamps.
Types are permanent
A Field's type cannot be changed after creation. If you need a different type, create a new Field (and optionally remove the old one). Plan your schema before entering production data where possible.
Ordering
Sections and their Fields can be rearranged to control the exact order users see when filling out an Item.
Next steps
Your Resource is ready for data. Head over to Working with Items to start capturing records.