# Feature planning: saved filters

## Who should receive saved filters first?

- Type: `review`
- Status: `recommended`
- Choice: Existing dashboard users
- Context: The first audience determines onboarding, defaults, and delivery scope.
- Reason: Known users provide evidence with the smallest delivery surface.

## What is the smallest useful delivery slice?

- Type: `auto`
- Status: `recommended`
- Choice: Private save, rename, and delete
- Context: The first release should test repeated filter use without building a full sharing system.
- Reason: One private vertical slice tests the feature promise safely.

## How should the first release be explained?

- Type: `auto`
- Status: `recommended`
- Choice: Inline help plus one README example
- Context: Users need one discoverable explanation independent of rollout scope.
- Reason: The smallest durable explanation is sufficient.

## Should shared team filters be part of the first public release?

- Type: `human`
- Status: `pending`
- Choice: No selection yet
- Context: Sharing changes permissions, ownership, migration, and the public product promise.
- Reason: Open