Kinabase Logo
Help & Support

Collection Lists

Organise complex data inside a record with inline lists of related items


**Collection List

**s let you attach multiple related records - such as order line items or bill-of-materials parts - within a single record, keeping everything together and rolling totals up automatically.

Each list has its own fields and calculated fields, and every action you take on the main record (duplicate, delete, restore) can include its list items. A list can also have Type

s, so mixed rows on one record keep the fields they need.


Why use collection lists?

Stay in context

View, add, and edit list items right inside a record, no extra tabs.

Automate roll-ups

Sums, averages, counts, and status fields update in real time.

Act in one click

Duplicate, export, delete, or restore a record and all its list items together.



1. Accessing the lists configuration

1. Open collection configuration

Go to the collection in the sidebar. Right-click it, or click the options menu (⋯), and select Configure.

2. Select Lists

This tab shows any existing lists and lets you add, remove, or edit them. Lists are hidden from the main navigation, so you'll only see them here or inside a record.


2. Creating or editing a list

1. Add a list

Click Add under Lists. Give the list a Name (e.g. Line Items, Components). Kinabase automatically labels each list item for you - no manual setup required.

2. Define fields

Add standard or calculated fields that belong exclusively to the list. Required fields in the collection stay required across every list.

3. Need unique IDs? Use a child collection

A list doesn't have identifiers. If each item needs its own ID, use a child collection instead and set Identifiers on its Details pane.

Read more about adding unique identifiers.

4. Save

Click Save to confirm. The list now appears under the Lists tab and inside each record.


5. Set the row order

Once the list has been saved, click Edit on it. On the Fields tab, under Sorting, select the Sort Field - for example a due date or a value - and turn on Invert Sort Direction to reverse the order. Click Update. Select Created At to keep rows in the order they were added.

Rows on the record, and on the printed record, follow this order, and a row you add or edit moves straight into place. Clicking a column header re-sorts only the table you're looking at, and isn't saved.

Read our Product Update for more.

6. Give a list types (optional)

Once the list has been saved, click Edit on it and open the Types tab. Click Add type, name the type and tick its fields. Type lifecycle and Required work as they do on a collection - see Types on lists and child collections.

Read our Product Update for more.


3. Choose where a list shows

By default, a list shows on the record's Details tab and when you add or edit a record. You can hide it from either, or show it only for particular types or workflow stages. The Visibility tab appears once the list has been saved.

  1. Open Configure and select Lists.
  2. Click Edit on the list and open Visibility.
  3. For Details and for Forms, select Hidden, Shown or Custom.
  4. If the list has types, tick A table for each type of followed by the list's name, for example A table for each type of part, to give each type its own section. Leave it unticked to keep one shared table.
  5. Click Save.
  • Hidden on Details takes the list off the Details tab, but it's still included when you print the record.
  • Hidden on Forms leaves the list out when you add or edit a record. People add rows from the list's heading on the Details tab instead.
  • Custom appears when the collection has types or a workflow. Click Add condition to show the list only for a particular type, workflow stage, or both.

This is the only place to set where a list shows - editing a type or a stage doesn't change it. An eye icon on the list's row shows when it's hidden or limited. The same choices are available for a field group; see Organise fields into groups.


4. Using lists in aggregations

  1. Open collection configuration and select Fields.
  2. Click + Add Field and select Aggregation.
  3. Open the dropdown for Target Collection and select your collection list.
  4. Select a link field from your collection list.
  5. Add any filters and the mode for your aggregation (e.g. Count, Sum, Average).
  6. Click + Add, then refresh your collection to see the new values.


Read more on Computed Fields.


5. Working with list items in a record

  1. Open any record and scroll to the inline table that represents the list.
  2. Add, edit, or delete items directly in the table or via the full-screen form. If the list has types, the form asks only for that type's fields. In a shared table, use the menu beside Add to add a row of a particular type; in a section per type, that section's Add, Import (.csv) and Export (.csv) stay with its type.
  3. Duplicate a list item - right-click any item and select Duplicate to open an add form pre-filled with the original values. Adjust what you need and save as a new entry. File attachments aren't copied.
  4. See roll-ups refresh instantly - totals, averages, or status indicators recalculate as soon as you change a list item.
  5. Bulk actions on list items - use checkboxes to select multiple items, then right-click for bulk operations:
    • Edit multiple - change a field value across all selected items at once.
    • Delete - remove multiple items in one action. A confirmation modal explains the 30-day recovery window.
    • Export (.csv) - download selected items to CSV.

    Bulk Delete requires the Bulk Delete permission to be enabled in your role settings.

  6. Record actions (duplicate, delete, restore)
    • Duplicate a record - Kinabase duplicates all its list items.
    • Delete a record - list items are deleted too, and appear in Recently Deleted under their own tab.
    • Restore a record - Kinabase restores all list items, keeping their links intact.



6. Turning a list into a child collection

Most lists work well embedded inside their parent record. If a list's items need their own page, their own search, or a permanent place in the sidebar, you can convert it into a Child Collection

- or create one directly, without an existing list.

1. Open collection configuration

Go to the collection in the sidebar, right-click it or click the options menu (⋯), and select Configure, then select Lists.

2. Create or convert

Select Add under Child collections to create one from scratch, including its initial fields. To convert an existing list instead, open its menu and select Convert to child collection, then confirm.

3. Find it in the sidebar

A child collection appears nested beneath its parent collection in the sidebar. Each item gets its own collection and record pages, and stays linked back to its parent record.

Its table on the parent record follows the child collection's own Sorting, set from its Configure screen under Fields - see Primary, Secondary, and Sort fields.

Existing items in a converted list remain available, and the field linking each item to its parent cannot be removed, redirected, or made optional.

To choose where its table shows on the parent record, see Choosing where a child collection shows.

Read our Product Update for more.


7. Choosing where a child collection shows

A child collection's table sits on its parent record. You can choose whether it shows on the parent's Details tab and when you add or edit the parent record, or only for particular types or workflow stages. The child collection's own page stays available, so people can still open and add those records there.

You'll need Configure Permission

for the parent collection. If you're unsure, ask your System admin.

1. Open Visibility

Open the parent collection, click the options menu (⋯) and select Configure. Under Setup, select Lists. Under Child collections, click the three-dot (⋯) Menu button on the child collection's row and select Visibility.

2. Set Details and Forms

For Details and for Forms, select Hidden, Shown or Custom. If the child collection has types, you can also tick A table for each type of followed by its name. Click Save.

  • Hidden on Details takes the table off the parent's Details tab. It's still included when you print the parent record.
  • Hidden on Forms leaves the table out when you add or edit the parent record. People add those records from the parent's Details tab, if the table shows there, or from the child collection's own page.
  • Custom appears when the parent collection has types or a workflow. Click Add condition to show the table only for particular types or stages of the parent record. If you add several conditions, all of them must match.

On the Lists page, an eye icon on the child collection's row shows that its table is hidden or limited. Editing a type or a stage doesn't change this setting.

How type and stage limits behave

  • With no setting, the table shows for every record.
  • A record with no type yet doesn't match a type condition, so the table stays hidden until a type is chosen. A record with no stage yet counts as being on the Default stage.
  • If a condition names a type or stage that no longer exists, Kinabase warns you, because that condition can never match.
  • Unknown Stage and Unknown Type, at the end of the list, match records whose stage or type has been removed. Conditions using them don't show a warning.

Read our Product Update for more.


8. Importing and exporting

Kinabase has intuitive importing and exporting functionality for list items, just as it does for top-level records, using the same column headings. See How CSV columns are named.

CSV import

Menu → Import (.csv) → select the target list.

CSV export

List menu → Export (.csv).

Bulk create via API

Add list records in bulk using the list's own collection ID through the Kinabase API.

Read our guidance for more on importing & exporting.


Utilising lists effectively

Collection lists are a powerful way to keep your data organised and exactly where you need it. Use them for order line items, quotes, or parts on a bill-of-materials.

Permissions & validation

  • List items always respect the collection's permission rules.
  • You need edit access to the record to add or change its list items.
  • A list cannot contain another list - this keeps structures simple.

Best practices

  • Start small - define core fields first, then add calculated fields for totals or status.
  • Plan ahead - lists cannot contain other lists; model deeper hierarchies with multiple collections if needed.
  • Review required fields - a required field in the collection remains required in every list item.
  • Test roll-ups - validate that your aggregation fields recalculate as expected before going live.

Need more help? Ask your System admin, or contact our support team via Help & Support.