Custom Fields
| Field | Value |
|---|---|
| Audience | public |
| Page type | reference |
| Area | sg-admin |
| Updated | 2026-05-14 |
The SG-Admin Custom Fields module — schema extension for Pages, Posts, Products, Custom Objects.
The Custom Fields module in the admin is the per-site surface for extending the default record schema. Operators add per-record-type fields (text, number, date, picker, etc.); the fields appear inside the corresponding record's edit surface; SG-Builder can read field values for conditional rendering. This page is the Reference definition.
What is this for?
Read this page when you want the structural definition of the Custom Fields module — the field-type catalog, scope per record-type, and where the field values surface.
Good use cases
- You are scoping site requirements that need extra metadata on records.
- You are explaining to a stakeholder how SGEN extends record schemas.
- You hit a "where do I add a custom field for this product type?" question.
What NOT to use this for
- Step-by-step procedures — open the relevant Guide.
- Per-release shipped change — open What's New or Changelog.
How this connects to other features
- SG-Admin Overview — parent surface.
- Pages — page records can carry custom fields.
- Blogs — post records can carry custom fields.
- Products — product records can carry custom fields.
- Custom Objects — custom-object records.
Where to find it
Open SG-Admin for the active site. Custom Fields is in the sidebar under the customization or content-types group. Each field is scoped during creation to a specific record type. Admin access is required.
Definition
A custom field in the admin is an additional schema field attached to a specific record type (Pages, Posts, Products, Custom Objects). Each field carries a label, type, validation rules, default value, and per-record-type scoping. Once added, the field appears inside every record of the scoped type.
The defining property is per-record-type scope. A custom field added to Pages does not appear on Posts; a field added to Products does not appear on Pages.
Purpose
Define the Custom Fields module as a Reference layer.
Scope
Covers field types, scoping, and surfacing. Does not cover per-step procedures (Guides) or per-release shipped change.
Field types
Text / textarea
Free-text fields with optional max-length validation.
Number
Numeric input with optional min/max validation.
Date / datetime
Date-pickers; useful for scheduled-event fields, expiration dates.
Select / multi-select
Picker from a defined option set.
Boolean
True/false toggle.
File / media
Reference to a Media Library asset.
Reference
Reference to another record (e.g., relate a Product to a Custom Object record).
Site · SG-Admin · Custom Fields
Field definitions
| Field name | Type | Scope | Required |
|---|---|---|---|
| Featured tag | Boolean | Posts | No |
| Reading time | Number | Posts | No |
| Product warranty | Select (1yr/2yr/lifetime) | Products | Yes |
| Event date | Datetime | Custom: Events | Yes |
Where field values surface
Record edit surface
The field appears inside the record's SG-Admin edit surface alongside the platform-default fields.
SG-Builder
Custom field values can be read by SG-Builder blocks for conditional rendering or content surfacing (e.g., a Product card that surfaces the warranty tag).
Search and filter
Some custom field types (select, boolean) support filter/search in the record inventory list.
Constraints and boundaries
Custom Fields is a Reference area for the schema extension surface.
Do not use for: per-step procedures (Guides), per-release shipped change.
Public boundary
This page is intentionally public-safe.
Examples
Example 1 — Operator adds a reading-time field to posts
Operator adds a Number field "Reading time" scoped to Posts. Editors fill the field per post; the value surfaces on Post Detail templates via SG-Builder.
Example 2 — Operator adds warranty info to products
Operator adds a Select field "Warranty" scoped to Products with options 1yr / 2yr / lifetime. The field appears on every product record; SG-Builder surfaces the value on the product detail page.
Example 3 — Operator scopes an event-date field to a custom Event type
Operator adds Datetime field "Event date" scoped to a custom Event object type. Event records carry the date; Posts blocks filtered by date range surface upcoming events.
Documentation guidance
Use this page as the structural definition for the Custom Fields module.
Reading order
Open this page when scoping schema extension. Pair with the relevant record-type Reference (Pages / Posts / Products / Custom Objects).
Related reading
- SG-Admin Overview — parent surface.
- Pages / Blogs / Products / Custom Objects — record types that carry custom fields.
Vocabulary cross-reference
- Custom field is one extra schema field on a record type.
- Field type is text / number / date / select / boolean / file / reference.
- Scope is which record type carries the field.
- Required flag marks a field that must be filled before saving the record.
Maintenance discipline
When Custom Fields changes across releases (new field type, new scope, new validation), update this Reference.
Related reading
| Topic |
|---|
| SG-Admin |
| Pages |
| Blogs |
| Products |
| Custom Objects |
