Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

3 acronyms in this thread; the most compressed thread commented on today has 6 acronyms.

[Thread #1013 for this comm, first seen 21st Jan 2026, 05:05] [FAQ] [Full list] [Contact] [Source code]

Preface

I got excited and didn’t properly read your post before I wrote out a huge reply. I thought your problem was the per-user mapping to different locations on your NAS or to different shares, but its specifically file ownership.
whoops.

Leaving this here anyways, in case someone finds it helpful.
I kinda address file ownership at the end, but I don’t think its really what you were looking for because it depends on every user having their own share.

Prerequisites

1. you need to be using Storage Templates.
2. you’re willing to change the storage labels for all existing users
   • if not, then change the storage labels for all users to something temporary and run the migration job before you begin. You’ll change it back later.
3. you’re willing to switch to NFS instead of samba, where each user gets their own share.
   • might not actually be necessary, but its what I use, so YMMV

Configuration

Volumes

In docker, you’ll need to set up an external NFS volume for every user. I use portainer to manage my docker stacks, and its pretty easy to set up NFS volumes. I’m not sure how to do it with raw docker, but I dont think its complicated.

Compose

in your docker compose files, include something like this

services:
  immich-server:
    # ...
    volumes:
      - ${UPLOAD_LOCATION}:/data
      - /etc/localtime:/etc/localtime:ro
     - type: volume
        source: user1-share
        target: /data/library/user1-intended-storage-label
        volume:
          subpath: path/to/photos/in/user1/share
    - type: volume
        source: user2-share
        target: /data/library/user2-intended-storage-label
        volume:
          subpath: path/to/photos/in/user2/share
    # and so on for every user
  # ...

volumes:
  model-cache:
  user1-share:
    external: true
  user2-share:
    external: true
  # and so on for every user

There are 3 things about this setup:

1. it does not scale automatically. this is fine as long as you don’t intend to be adding/removing users often.
2. it is only saving the photos and videos. all thumbnails and transcoded videos, etc, get saved to ${UPLOAD_LOCATION}. For me this is fine, I dont want to pollute my NAS with a bunch of transient data, but if you want that info then for every user, in addition to the target: /data/library/user1 target you’ll also need a target: /data/thumbs/user1, target: /data/encoded-video/user1, etc.
3. If there is already data at the target, when you mount this volume it will mask that data. This is why it is important that no users exist with that storage label prior to this change, else that data will get hidden.

You may also want to add similar volumes for external libraries (I gave every user an external “archive” library for their old photos) like this:

    - type: volume
        source: user1-share
        target: /unique/path/to/this/users/archive
        volume:
          subpath: path/to/photo/archive/on/share

and then you’ll need to go and add that target as an external library in the admin setup.
and once immich allows sharing external libraries (or turning external libraries into sharable albums) I’ll also include a volume for a shared archive.

Migrate

redeploy, change your user storage labels to match the targets, and run the migration job (or create the users with matching storage labels).

File ownership

I honestly don’t think its important, as long as your user has full access to the files, its fine. But if you insist then you have a separate share for every user and set up the NFS server for that share to squash all to that share’s user. Its a little less secure, but you’ll only be allowing requests from that single IP, and there will only be a request from a single user from that server anyways.
Synology unfortunately doesn’t support this, they only allow squashing to admin or guest (or disable squashing).

Generally, accessing files both as a share and through an app is not well supported. If Immich doesn’t support setting ownership, you might be able to patch it to add the feature.

Otherwise, I’d probably stick to the user-group model you have currently, and do the chown/chmod. Immich should be able to fully manage files as long as it has the group permissions necessary (g+rw).

You can configure samba to handle the permissions, but immich will need to connect to the user’s share using their password (no ideal)

In smb.conf for each user’s share

[user_media]
   path = /path/to/user/media
   valid users = username, immich
   force user = username  # This makes all files.  appear as owned by the user
   force group = media
   create mask = 0660
   directory mask = 0770

Alternatively you can use setguid with your media group:

chmod g+s /path/to/media/dirs
chown -R :media /path/to/media/dirs
chmod 2770 /path/to/media/dirs. (2 = SetGID, 770 = rwx for user and group)

• Any new file created by Immich will automatically belong to the media group
• The SetGID bit ensures files inherit the parent directory’s group
• All users (including Immich) can read/write files as long as they’re in the media group
• Individual users still “own” their files (UID stays as the original user when they upload via Samba)

Set the Immich instance to run as the UID that owns the media files?

I can only think of two ways if the top of my head:

• Immich runs as root and sets ownership (sounds unsafe)
• Immich is the owner of all the files, but each user has a specific group (bobs-photos) of which Immich and the user are members. Then use the setgid bit to set group ownership and make it g+rwx.

Both sound pretty brittle to me, though, and I haven’t tested this specifically.