Overview
Collections let you build your own structured lists inside Scrambl when no built-in module fits. Each collection is a table of entries with fields you define — think of an asset register, a software license tracker, a recipe book, or a list of office locations. Entries behave like first-class records: they get their own detail page, can hold documents and notes, and can link to contacts, projects, and other collections.
Open Collections to see every collection you have access to, as a Deck of cards (the default) or a List, each showing its entry count and last update. Collections you use often can also be pinned into a sidebar section so they sit alongside built-in modules.
When to use a collection
- Structured data with no home: equipment, licenses, policies, locations, product lines — anything you are currently keeping in a spreadsheet.
- Reference lists for custom fields: collections can serve as the option source for reference fields elsewhere in the workspace.
- Connected registers: because entries can link to contacts, projects, and other collections, a collection can anchor real workflows instead of sitting in isolation.
If the thing you are tracking is a client, project, task, or contact, use the built-in module instead — collections are for everything else.
What makes up a collection
| Part | Details |
|---|---|
| Identity | Name, icon, description, and a URL slug unique to your workspace. |
| Fields | Custom fields of many types: short and long text, rich text, numbers, percentages, currency, dates and times, single and multi select, checkboxes, references to other records, people, files, URLs, and calculated fields (formula, lookup, rollup). |
| Record tabs | Optional tabs on each entry — Documents & links, Discussions, and Notes are on by default; Projects, Contacts, and Communications can be switched on per collection. |
| Links | Relationships to other collections, with one-to-one, one-to-many, many-to-one, or many-to-many connection types. |
| Visibility | Private (only you), Limited (only people you invite), or Team (everyone in your organization). Team is the default. |
Inside an entry
Each entry opens to an Overview of its fields, editable inline. Around it, the tabs your collection has enabled appear — Documents & links, Discussions, Notes, Projects, Contacts, and Communications — plus one tab for each relationship you have configured, labeled with the name you gave the link.
Best practice: Keep one collection per kind of thing. If you find yourself adding a field like "Category" with wildly different values ("laptop", "policy", "office"), that is usually two or three collections wearing one name — and separate collections make relationships and permissions much cleaner.
Plans
Collections are included from the Core plan: Core allows 10 collections, and Pro and Business are unlimited. The Free plan doesn't include collections.
Next steps
- Create your first one with Build a collection.
- Bring existing spreadsheet data in with Import and export collection entries.