immich-app/immich

[Feature] Per user "minimum face count"

Open

#21,279 opened on Aug 26, 2025

View on GitHub
 (4 comments) (2 reactions) (0 assignees)TypeScript (100,600 stars) (5,601 forks)batch import
good first issue

Description

Each individual user should be able to specify a "minimum face count" that filters out people on the /people endpoint & associated page. This should be added as a user preference (probably at people.minimumFaces), and can be set to any number, with 0 implying that no people are filtered out of view.

Background

There is a server config option (machineLearning.facialRecognition.minFaces), that is used during the clustering process to determine at what threshold a Person is created. This same configuration setting is being used as a global cutoff for the /people endpoint, and has led to some confusion.

Contributor guide

Tech stack
typescript
Domain
full stack
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Immich architecture overviewTypeScript/Node.js basicsREST API understanding
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
The issue requests a per user 'minimum face count' preference. First, examine how existing user preferences are stored and retrieved (likely in a user preferences service or similar). Then, locate the `/people` endpoint and its associated controller/service to understand how the global config `machineLearning.facialRecognition.minFaces` is currently applied. Implement a new preference field `people.minimumFaces` in the user preferences schema, defaulting to 0. Modify the endpoint to filter people based on the user's preference instead of the global config. Finally, add a UI component in the user settings page to allow users to set this value. Ensure backward compatibility for users without the preference set.