Objects
Object settings reference
Reference every major object settings group: base, view, table, filters, redirect, portal, automation, and advanced.
Object settings reference
Object settings control how records behave in the staff workspace, customer portal, public forms, tables, filters, workflows, and integrations. Treat this page as the configuration checklist for any object before it goes live.
Settings groups
| Group | Important settings | What they affect |
|---|---|---|
| Base | Enable comments, enabled state, featured state, readonly state, all-staff access. | Whether the object appears and how staff interact with it. |
| View | Expanded view, record scrolling, page icon, menu icon. | The record detail layout and navigation experience. |
| Table | Show created by, created at, image, object filter, table actions, edit, delete, archival. | Object list behaviour and table actions. |
| Form | Show reference, image, alias, empty fields, bulk insert, bulk update. | Create, edit, and read-only record forms. |
| Filters | Configured filter attributes with label, name, field type, data type, and namespace settings. | Filter panels and saved object filters. |
| Redirect | Redirect after record creation, commonly list or view. | User flow after submission. |
| Children | Child record support, max child records, inline child forms. | Hierarchies, parent-child objects, and protected children. |
| Customer | Readonly, featured, add, edit, delete, maximum records. | Customer portal object access. |
| Public | Public flag and public code. | Anonymous /form/<code> submissions. |
| Omnichannel | Phone and email field mapping. | Matching inbound messages to records. |
| Automation | Async processing and automation behaviour. | Background processing and event automation. |
| Advanced | Indexing, document linking, group template, static objects, engine. | Search, document context, grouping, associations, and storage. |
Recommended review before publishing
- Confirm labels and descriptions are user-facing.
- Confirm namespace and engine are correct before records are created.
- Check table actions against the role model.
- Test filters with real data and least-privilege users.
- Review customer and public flags separately from staff access.
- Confirm automation and scripts run against expected test records.