[BUG] Partner Sharing - Unable to delete photo

[yurividal]

The bug

When partner sharing on the time-line is enabled, the user who doesn't own the picture cannot delete a shared picture. The delete button does nothing.
If this is by design, then the button needs to be hidden, or some sort of UI element to tell the user he can't delete partner's photos.
Even better would be if there was an option in the settings to allow a user to do such a thing.

The OS that Immich Server is running on

Ubuntu 22.04

Version of Immich Server

V1.88.1

Version of Immich Mobile App

V1.88.1

Platform with the issue

• Server
• Web
• Mobile

Your docker-compose.yml content

Same as example one.

Your .env content

Same as example one

Reproduction steps

1. Enable partner sharing
2. Enable shared photos on timeline
3. Try to delete a photo that belongs to your partner. Mobile and Web
...

Additional information

No response

[BarrettLowe]

Looks like the following may be the culprit:

immich/web/src/lib/components/photos-page/actions/delete-assets.svelte

Line 40 in 8a2b36a

const ids = Array.from(getOwnedAssets())

I don't know typescript so I'm having a hard time tracking this backward but at an initial glance, it may work to change this to use getAssets instead...?

[alextran1502]

This is as designed. Let me think of a way to make it less confused

[yurividal]

This is as designed. Let me think of a way to make it less confused

Thought it would be as design. Indeed a UI hint is needed here.

Even better would be if there was a option to allow deletion of partners photos.

(Example: my wife is constantly taking pictures of receipts or things she only needs for a few minutes, and never remembers to delete them from immich. I'd love to be able to clean these every now and then, instead of filling our precious storage space with useless pictures)

[Fl0ete]

This is as designed. Let me think of a way to make it less confused

Thought it would be as design. Indeed a UI hint is needed here.

Even better would be if there was a option to allow deletion of partners photos.

(Example: my wife is constantly taking pictures of receipts or things she only needs for a few minutes, and never remembers to delete them from immich. I'd love to be able to clean these every now and then, instead of filling our precious storage space with useless pictures)

I'd also love to see this. In my case, I am always the one "thinning out" the photos, deleteing blurred ones, keeping only the best shot of many of the same motive. And I would love to just show my partners photos in my timeline (especially with kids), but having them raw is not really satisfying.

Kind of a big ask, but for me the optimal solution would be something like this: I mark the pictures for deletion and my partner gets a notification/hint to look over them and confirm. This way, she doesn't have the work and can still be sure I delete nothing important to her.

[Jab2870]

I'm not sure if this is really the correct place to ask, but I would really like to see the partner sharing to allow a lot more control.

Deleting photos is certainly part of that, but other stuff like being able to add a partner's photos to an album etc.

[andrewdcaudle]

I concur with a setting that would allow partners to delete the other's images.

[Tonylolo]

Yes , very good idea, partner would become a real user. 2 users of 1 photo server, a lot of case for family i think.
Thk for taking in consideration

[krin-san]

I concur with a setting that would allow partners to delete the other's images.

I actually tried to find if this option exists on /user-settings?isOpen=partner-sharing page. Imagined, it could look like that:

[jrasm91]

This is working as designed and a limitation of the current partner sharing implementation, so I'm going to convert this to a discussion where different enhancement options can be discussed instead.

[eygraber]

I think the other app has a somewhat decent model for this. I can "save" photos shared with me, and then that photo becomes mine. My faces are applied to it, I can edit it, and I can delete it. I'm pretty sure they're not duplicating the photo itself, and I just get my own metadata.

I would love to share faces and exif data as well, but I guess that's a separate issue.

[yurividal]

Thanks for converting this into a discussion.
I believe the key point here is "choice".
In my opinion, a simple checkbook, or drop-down to allow full control over shared items should be added to the partner sharing setup.
As an admin of my immich instance, (and the only one who really cares about my family memories being clean and organized 😅) it is frustrating to have to borrow my partners phone in order to delete a bunch of random screenshots and other useless files.

[yurividal]

HI @alextran1502
Has this been considered by the dev team? Should we get our hopes up that this might one day be implemented?

[oscarnorberg]

I am missing this feature as well, in my family I am the one managing our media server and regularly go through our photos, create albums and delete photos and videos that are not needed. The fact that I cannot delete a screenshot or as someone mentioned above, a photo of a receipt is very annoying.

I support having an option under Partner Sharing where you as a user can allow your partner to delete items that you have uploaded.

[alextran1502]

We want to have this feature. It requires some extensive refactoring of the permission model which is currently being worked on

[Digmarx]

This is good news, as the lack of this feature is a large barrier to use for people with my use case (multiple family members with multiple devices uploading, 1 administrator curating and removing cruft like screenshots, blurry pics, etc)

[benlinton]

+1 to this feature request.

As a temporary work around, I may create a nightly job that iterates through "Archive Later" and "Trash Later" albums - so we can curate photos together from multiple accounts.

[yurividal]

My workaround is simply having a alternative browser (on my phone and on my PC) that is logged in with my wife's account. Then whenever I see junk in immich, I just open that browser to my immich instance and use it to delete the images.

[anst84]

If your wife too has Sharing enabled for your library, how do you filter out which photos that is yours? In my case we both have each others photos in our timelines, but I'm unable to find a way to filter on "owner". The only way I can work around this is by disabling sharing.

[benlinton]

Here's auto-archive and auto-trash scripts for anyone that wants them.

You can run these on a cron to work around having many users.

https://github.com/benlinton/immich-tools

[yurividal]

Thanks. I tried using your approach. The script finds the album, finds the assets and says it marked them as achieved. But, when I open immich they are still there, and not achieved.

I also tried adapting it to use the delete method but couldn't get it to work.
I'm probably doing something wrong...

[benlinton]

I've improved these scripts a lot since posting. I added them to a git repo for you. I hope they help.
https://github.com/benlinton/immich-tools

[benlinton]

It probably wasn't obvious until this version - but if you don't include the --allow-single-album flag - the archive script will skip assets that have not yet been added to a secondary album (as a safety net to avoid archived photos getting lost in a black hole). Try using --verbose mode to see what's going on under the hood. Also make sure each user in the config has their own API key or it probably won't work. Take care.

[orange-buffalo]

My workaround is to use this Tampermonkey (or similar) script. It will add a button to the photo view that issues an API call with a token depending on the owner of the asset:

// ==UserScript==
// @name         Delete Immich photo
// @version      2025-02-23
// @description  Removes shared photos from Immich
// @author       orange-buffalo
// @match        https://<your host>/*
// @grant        none
// ==/UserScript==

(function() {
    'use strict';

    const usersToKeys = {
        "<id>": "<key>",
    };

    async function fetchAssetOwner(assetId) {
        const response = await fetch(`/api/assets/${assetId}`, {
            method: 'GET',
        });
        if (!response.ok) throw new Error('Failed to fetch asset data');
        const data = await response.json();
        return data.ownerId;
    }

    function extractAssetIdFromUrl() {
        const match = location.pathname.match(/.*?photos\/([a-f0-9\-]+)/);
        if (!match) {
            throw Error("Invalid path, cannot extract asset ID");
        }
        return match[1];
    }

    async function deleteAsset(assetId, apiKey) {
        const response = await fetch('/api/assets', {
            method: 'DELETE',
            headers: {
                'Content-Type': 'application/json',
                'x-api-key': apiKey
            },
            credentials: "omit",
            body: JSON.stringify({ ids: [assetId], force: false })
        });
        if (!response.ok) throw new Error('Failed to delete asset');
        console.log('Deleted Asset ID:', assetId);
    }

    async function deletePhoto() {
        try {
            const assetId = extractAssetIdFromUrl();
            console.log('Extracted assetID: ', assetId);
            const ownerId = await fetchAssetOwner(assetId);
            console.log('Asset owner is: ', ownerId);
            const apiKey = usersToKeys[ownerId];
            if (!apiKey) {
                throw Error('Cannot find key for user: ' + ownerId);
            }
            await deleteAsset(assetId, apiKey);
            alert("Photo moved to Trash");
        } catch (e) {
            alert('Failed to delete: ' + e.message);
        }
    }

    function addButton() {
        const navbar = document.querySelector('[data-testid="asset-viewer-navbar-actions"]');
        if (!navbar || document.querySelector('#custom-log-button')) return;

        const button = document.createElement('button');
        button.id = 'custom-log-button';
        button.textContent = 'Del';
        button.className = 'flex place-content-center place-items-center rounded-full bg-transparent hover:bg-immich-bg/30 text-white p-3 transition-all';
        button.onclick = deletePhoto;

        navbar.appendChild(button);
    }

    function waitForNavbar() {
        const interval = setInterval(addButton, 1000);
    }

    waitForNavbar();
})();

For it to work, you need to grab user IDs and create API keys for them. Getting user ID might be tricky. One option is to use /api/users/me with the corresponding key. Another is to check Immich responses in Network tab and extract ownerId from the JSON.

[bo0tzz]

Folks, if your comment amounts to "I want this too" then please just use the upvote button on the original post.

[elgatho]

definetley this is confusing, maybe adding on the main page to turn off partner photos switch, on/off will be a good workaround for now. now i'm checking multiple photos to remove and some of them are removed some not, so we are duplicating job

[kellergoech]

Is there any progress on this part?

[bo0tzz]

https://justinmayer.com/posts/any-updates/