Right Management for a family
I am about to setup my Immich instance for me and my family (2 parents/ 1 Child). Regarding the rights management I have some ideas in mind but don't know if I can make them happen.
Optimal solution:
- Everyone has his own account with the own pictures. (Done)
- Everyone makes own pictures and family pictures. The pictures for the family we want to share. (Manually)
- If a shared family picture is edited/removed each person should decide themself if they want to go with the change.
The feature "Partner Sharing" is not sufficient for me. Me and my partner don't want to be overloaded with the pictures from the other person.
So I was exploring the share album function to see if this is able to help me:
Setup: I was creating a Shared Album in my account and shared this to my partner. As editor.
- I can add pictures to this album and my partner can add pictures to this album. (Perfect)
- I can remove my pictures and the pictures from my partner from album. (fine)
- I can not see the pictures added by my partner in my timeline / map. Is this a bug or is it intended? (missing)
- My Partner can not remove my pictures from the album. Is this a bug or feature that my partner (editor) can not remove the pictures from my album? (missing)
- To get a own copy of the shared pictures i tried to make the following:
1. From my partners account I wanted to make a copy of the pictures to an new album.
2. selecting all pictures
3. Add to album
4. Created a new album.
5. "Info Added 145 assets to copy_family3"
6. The new created album is now empty.
- Event if i want to copy them again to the new created album it is stating that the pictures already exists.
- Is this a bug or do I miss something?
It will even gets more complicated after my small one is getting to make own pictures which needs to be saved and shared.
How do you realize your family rights management? Did I missed a function in Immich which makes this easier?
4 Replies
:wave: Hey @Fritjof,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.There is a whole rewrite of the permission model planned, that is supposed to allow the things you mention. For reference there is a meta issue: #12614
Thank you for this link. I will read this to get an overview.