For the complete documentation index, see llms.txt. This page is also available as Markdown.
Collections
Collections hold your records — schema, data, and triggers in one place.
A collection holds your records. Its schema defines the fields, types, and validation; Norbix then generates a full CRUD + query API over the collection, with record-level ownership and triggers.
Database → Collections.
What you can do here
The list shows every published collection with its Status — Published · v2, or Published · v2 · draft pending when unpublished edits exist on top. Schemas that were never published sit below in Schemas under development; publish one to start adding records. A flame icon in the Triggers column marks collections that have triggers and jumps to their Triggers tab; the row menu has Edit schema.
Add New creates a collection by creating its schema — see Build a Schema for the full walkthrough (drafts, versions, publishing). Click a collection to work with its records in the generated grid and form, define triggers that fire on OnInserted, OnUpdated, or OnDeleted, and check index coverage for sorting on the List tab.
Records respect ownership: switch Records have an owner on in the collection's Settings tab and the end-user API can be limited to "own" records (findOwn), so an app user only reads what belongs to them.
