immich-app/immich

Manage location shows partner assets as if they were editable

Chiusa

#21.471 aperta il 31 ago 2025

Vedi su GitHubGuida contributor
 (3 commenti) (0 reazioni) (0 assegnatari)TypeScript (5601 fork)batch import
good first issue🖥️web

Metriche repository

Star
 (100.600 stelle)
Metriche merge PR
 (Merge medio 5g 3h) (258 PR mergiate in 30 g)

Descrizione

I have searched the existing issues, both open and closed, to make sure this is not a duplicate report.

  • Yes

The bug

I have three accounts in my server I was testing the "manage location" utility The problem that I have is that it show all the assets, including the ones not belonging to my account. When I try to change the location of a picture from a different account it is doing nothing (as expected) But would be nice that utility only show assets from my account or a banner that explain that it will not modify other accounts

The OS that Immich Server is running on

Ubuntu 24.04

Version of Immich Server

1.140.1

Version of Immich Mobile App

1.140

Platform with the issue

  • Server
  • Web
  • Mobile

Device make and model

No response

Your docker-compose.yml content

Standard

Your .env content

Standard

Reproduction steps

...

Relevant log output

Additional information

No response

Guida contributor

Direzione di ricerca
The issue describes that the 'Manage location' view shows assets from all accounts, but only allows modification of own assets. The fix likely involves filtering assets by ownership in the backend endpoint that serves assets for the location management page. Investigate the location management controller and service in the Immich repo (e.g., in server/src/domains/location/). Check if there is a user ID parameter or authentication context that should be used to filter assets. Review existing permission checks for other similar features (e.g., album management) to ensure consistency.
Tech stack
typescriptrest apireact
Dominio
backendfrontend
Tipo issue
Bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 ore
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
Nuova
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
Abbastanza chiara
Prerequisiti
Understanding of multi user photo managementBasic knowledge of REST APIs
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
40