Feedback lands in one pool, and products cut priorities, specs, Ask and Radar to the product they belong to. Nothing is siloed — a signal that matters to two products isn't trapped in one, and switching products never hides work, only narrows the view.
01A filter, not a wall
02Manage products
Settings → Products. Create, rename and retire products there — the settings page owns product management, so the rest of the app stays about the work.
03Where feedback homes
New feedback lands on the product its source belongs to — a Slack channel's configured product, or the product you choose at import. One source, one home, no guessing about what a message meant.
04Filtering by product
The product filter runs through the surfaces: priorities, the roadmap and Radar. Same pool, narrower question.
05Projects group work under a product
A project is a child of a product — a place to group related priorities and specs while they're being worked. The hierarchy stays two levels deep on purpose.
06Can Annsa handle multiple products?
Yes — feedback from every product lands in one pool, and products act as filters across priorities, specs, Ask and Radar. Manage them at Settings → Products. Signals aren't walled into a product, so a theme crossing two products stays visible in both.