Collections

A collection is a folder for projects. It is also where several per-folder settings live: custom vocabulary, a linked dictionary, meeting notetaker behaviour, and who else can reach what is filed there.

Collections appear in the left sidebar of the dashboard, with their sub-collections nested underneath.

Creating collections

A collection: in the left sidebar, click Collection, or the + next to the Collections header.

A sub-collection: hover a collection in the sidebar and click the folder-plus icon, type a name, and press Enter. The parent expands to show it.

Collections go one level deep. A sub-collection cannot have sub-collections of its own — a folder tree that keeps nesting is harder to search than a flat list with good names.

A few naming rules: names are unique across your whole organization, are stored in lower case, and are capped at 50 characters. Accents and apostrophes are fine — réunions and l'équipe stay as you typed them.

Colours and emoji

Open a collection and click Collection settings at the top to give it an emoji and a colour. Both show in the sidebar, so a long list stays scannable.

Pick from thirteen colours, or the crossed-out swatch for no colour at all. Colours are theme-aware: a collection painted in light mode still reads in dark mode.

Appearance is deliberately never inherited. A sub-collection always keeps its own emoji and colour, because repeating the parent's down a stack of sidebar rows makes them harder to tell apart, not easier. A sub-collection with no colour of its own shows its parent's.

Filing projects

• Drag a project from the dashboard onto any collection or sub-collection in the sidebar.
• Select several projects and use the Move button.

Sub-collections and inherited settings

A new sub-collection starts out following its parent for everything except its name, emoji and colour. Five groups can be inherited:

• Custom vocabulary
• Dictionary
• Meeting notetaker settings
• Sharing — who can reach it
• Privacy defaults

In the sub-collection's settings each of these shows a badge — Inherited or Own — with an Override switch. Leave it inherited and later changes to the parent follow automatically. Switch it on and the sub-collection keeps its own values from then on, and stops following the parent for that group only.

Inheritance is per group, so a sub-collection can carry its own vocabulary while still sharing with exactly the people its parent does.

"Inherited" and "empty" are not the same thing. Clearing a sub-collection's vocabulary list while it is set to Own means "no vocabulary here", not "use the parent's".

Moving a collection

In a sub-collection's settings, Parent collection moves it under a different collection. Choosing the empty option promotes it back to a top-level collection.

Two limits follow from the one-level rule: a collection that has sub-collections of its own cannot become a sub-collection, and you need edit access to the collection you are moving it into.

Moving a sub-collection that still inherits sharing re-points it at the new parent's people.

Vocabulary, dictionaries and meeting settings

Per collection you can set:

• Custom vocabulary — terms applied to every file uploaded into the collection.
• A linked dictionary — preselected in the upload dialog for this collection. See Organization settings.
• Meeting notetaker settings — how the meeting bot behaves for recordings filed here, including whether it writes notes and who gets the email summary.

Sharing a collection

Sharing is what makes a collection a team folder rather than a personal one: share it once, and everyone on it can reach every project in it, including the ones added later.

The controls live under Share collection in the same settings dialog. See Sharing and Access for how this fits together with membership and roles, and for why the section is sometimes not shown.

Deleting a collection

Use the trash icon next to a collection in the sidebar.

• Deleting a top-level collection also deletes its sub-collections.
• The projects inside are not deleted by default — they are moved back to All Projects. Tick the option in the confirmation dialog if you want them deleted too.
• Deletion is blocked while the collection, or one of its sub-collections, still holds projects belonging to other people. They need to move their projects out first; the message names who.