> ## Documentation Index
> Fetch the complete documentation index at: https://docs.laneapp.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Areas

> The map of your product. Lane uses it to sort feedback as it arrives, so you can see which parts of your product customers care about most.

Product Areas are the map of your product: Onboarding, Billing, Reporting, Integrations, whatever the meaningful parts of your product are. Once they're set, Lane sorts every piece of [feedback](/insights) into the right areas as it arrives, with no manual tagging, and carries them onto [Signals](/signals). That's what lets you answer "where is demand concentrated?" with real numbers, and filter your Signals down to the part of the product you own.

A single piece of feedback can touch more than one area: a request about "exporting a report" can belong to both Reporting and Integrations.

## Start from the starter set

New workspaces come with a starter set of common Product Areas, each with a description, so feedback is sorted from the very first item. Open **Settings → Product areas** and make them yours: rename the ones that are close, remove the ones that don't fit, and add the parts of your product that are missing.

## Add or edit an area

Choose **Add Product Area**, or click an area to edit it. Each area has:

* **Name**: what your team calls this part of the product.
* **Colour**: pick one from the icon next to the name, so the area is easy to spot across Lane.
* **Description**: a short explanation of what belongs here.

The description isn't cosmetic. Lane reads it to decide where feedback goes, so a clear description, what the area covers and what it doesn't, directly improves how accurately feedback is sorted. It's the single highest-leverage thing you can do to keep your feedback well organized.

<Tip>
  Write descriptions for a reader who doesn't know your product. "Billing — invoices, payment methods, plan changes, and dunning" sorts far more accurately than "Billing — billing stuff."
</Tip>

## Where Product Areas show up

* **Feedback** is sorted into its areas automatically. You can change an item's areas by hand at any time.
* **Signals** carry the areas of the feedback behind them, shown as chips in the list. Filter the Signals list by area, or choose **No Product Area** to find what isn't mapped yet.
* **Ask Lane** knows your areas, so you can ask "what's the top request in Billing this month?"

## Best practices

* **Keep the set small and stable.** A dozen clear areas beat fifty overlapping ones. Areas are most useful when everyone means the same thing by them.
* **Invest in descriptions.** Treat them as instructions to Lane, not labels for people.
* **Revisit as the product grows.** When you ship a genuinely new part of the product, add an area for it so its feedback has somewhere to land.

## FAQs

**Q: Can one item belong to more than one area?**\
A: Yes. Feedback and Signals can each carry several areas.

**Q: How does Lane decide which area feedback goes to?**\
A: It reads each area's name and description, which is why good descriptions matter.

**Q: Where do I manage Product Areas?**\
A: In **Settings → Product areas**.

**Q: What happens if I delete an area?**\
A: It's removed straight away from every piece of feedback and Signal that had it, and those show as **No Product Area**. Deleting takes effect immediately, so rename or edit an area if you only want to change it.

**Q: What if I don't set any up?**\
A: Feedback is still captured and grouped into Signals, but it won't be organized by area, and you won't see where demand is concentrated.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.