Groups
Groups organise people by department — Engineering, Go-to-market, Leadership — and are used when scoping who a piece of work belongs to.
What groups do today
They structure membership lists, and they scope what a member sees: a fact is visible when the episode behind it is ungrouped, or carries a group you are in. Admins are not scoped by groups.
Tagging is content-level
Each episode is tagged by what it is about, not by the connector it arrived through. One Notion workspace holding both Finance and Marketing pages tags each page with the department that page belongs to. The connector's own group mapping is only the fallback, used when the content does not say — so a piece of work that spans the company, or that cannot be placed, stays as wide as its source already was.
The teams you name in the interview are set up as groups during onboarding, whether you pilot with one of them or open Flipper to the whole company. One group is enough for this to work: every item is still judged against it, and what doesn't belong stays out rather than being swept in.
Anything that can't be placed goes to an admin
What neither the content nor the source can place lands ungrouped, which means the whole workspace can read it. That is a queue, not a resting state: Governance shows an admin how many items are waiting and lets them allocate each one in a click.
Those allocations are the training signal. Flipper feeds an admin's own past decisions back into the next classification, so it learns how your company files things — that #launch-eu is go-to-market, that the board pack is leadership — without anyone writing a rule.
