Overview

Building a collection has four stages: create it, define its fields, add entries, and connect it to the rest of your workspace. You can do the first two in a single dialog and refine everything later from the collection's Settings tab.

Who can do this

  • Required access: an access level that includes Collections - Standard Access or Collections - Full Access.
  • Default access levels that include it: Team Member, Accountant, and System Administrator.
  • Owners and admins: always allowed. Workspace owners and admins are not limited by access levels.
  • Record tabs, links between collections, and reminder rules need Collections - Full Access.
  • Personal accounts: The Family Admin, Family Member, and Limited Member presets include this access. The space owner and admins can always do it.

Owners and admins review and change access levels in Settings → Administration → Members → Access levels.

Step 1: Create the collection

  1. Open Collections and choose New collection.
  2. In a personal (family) space, choose a starting point under Start with: Blank, Bills, Recipes, or Trip Ideas.
  3. Enter a Name and pick an icon. Use Add description so teammates know what belongs here.
  4. Open More options to edit the Slug (used in URLs, generated from the name and checked for availability as you type) and choose Visibility: Private (only you), Limited (only people you add under Invite members), or Team (everyone in your organization, the default).
  5. Under Record tabs, toggle what each entry should include. Documents & links, Discussions, and Notes start on; Projects, Contacts, and Communications start off.
  6. Optionally add starting fields with Add field, then choose Create.

Step 2: Define fields

Fields live in the collection's Settings tab under Custom fields. Field types are Short text, Long text, Rich text, Number, Percentage, Currency, Date, Date & time, Time, Single select, Multi-select, Checkbox, Reference, Multi-reference, Person, People, Single file, Attachments, URL, Formula, Lookup, and Rollup.

  • Every collection has a built-in primary Name column; you can rename its label in Settings to match your data — "Asset", "License", "Location".
  • Calculated fields are computed automatically from other data, so they are read-only when you create entries.

Step 3: Add entries

  1. Open the collection. The All entries tab is a full table with sorting, filtering, and your fields as columns.
  2. Choose New entry, fill in the fields in the New entry dialog, and click Create entry.
  3. For bulk data, use Settings → Data → Import Entries to load a CSV. Download the import template first so your columns match.

Two mechanisms connect entries outward:

  • Linked collections: in Settings → Record setup, choose Add link to relate this collection to another. Pick the target collection, name how the link appears on each side, and choose a connection type — one to one, one to many, many to one, or many to many. Each link becomes a tab on entry pages where you attach related entries.
  • Reference fields: add a field of type Reference or Multi-Reference to point an entry at records in other modules, such as an entity, project, or task.

If you enabled the Projects or Contacts tabs, you can also attach projects and contacts directly to individual entries from those tabs.

Best practice: Name both sides of a link from the reader's point of view. For an Assets-to-Employees link, "Assigned assets" on the employee and "Assigned to" on the asset reads far better than "Employees" and "Assets".


Troubleshooting

IssueWhat to check
A teammate cannot see the collection.Check its visibility — Private and Limited collections are hidden from everyone not invited. Only the collection owner can change visibility or manage members.
An expected tab is missing on entries.Record tabs are toggled per collection in Settings → Record setup. Discussions and Communications tabs only work where those modules are available.
You cannot create another collection.Core allows 10 collections and Free none; the create dialog shows your usage against the limit.
Deleting a collection warns about custom fields.Deleting removes the collection and all its entries permanently, and any custom fields using it as an option source lose their options.

Next steps

  • Share the collection and pin it to the sidebar.
  • Import existing data from a spreadsheet.