Instance · CMS
Collections Introduction
Last updated 1 November 2026
Turn a set of records into a list page and a details page, each with its own layout.
A collection turns a set of records into two kinds of page. A list page shows many items, and a details page shows one. You design each with its own layout in the CMS. Use one for a blog, a staff directory or a product range: any set of items that needs a list and a page for each.
Where to find collections
In the admin, open CMS and choose Collections. The list shows every collection; open one to edit it, or add a new one.
The parts of a collection
| Tab | What you set |
|---|---|
| Details | The address (slug), the data the collection reads, and the layout |
| List Layout | The template for the list page |
| Details Layout | The template for the page of one item |
| Security | Authorization policies that decide who may see it |
| Cache | How long the page is cached, and how |
Example: a team directory
- Add a collection with the slug
team, reading your staff records. - In List Layout, show each person's name and photo, linked to their page.
- In Details Layout, show one person's full profile.
- Leave Security empty for a public page, or add a policy to limit it to members.
Note
These steps describe the collection screens as documented in the Insites Logic Engine CMS reference. They were not run, because adding a collection writes to the instance.
Common mistakes
- Forgetting the details page. A link from the list page then leads to an empty layout.
- Expecting a missing item to return 404. The details layout answers 200 even when no item matches, so check the item exists and show a not-found message.
- Showing private records on a public collection. Add a policy in Security.