Skip to content

Sharing: Multi-user / multi-library support with private and shared photos/albums #98

Open

Description

@rkkoszewski

It would be great to be able to share a PhotoPrism server between several people, each having their own private pictures/albums, and pictures/albums that could be shared with other users on the same server.

This would probably increase the complexity of the project quite a bit as a whole session/login/profile system would need to be implemented and also handle how to manage the pictures (All pictures in a single folder and assigned to different users by Database, a special folder structure, etc), most likely not compatible with how it works now.

I was not able to find out from the Wiki about what kind depth is PhotoPrism aiming at regarding photo management. Any input on this from the Devs?

Activity

  1. added
    ideaFeedback wanted / feature request
    on Feb 26, 2019
  2. lastzero commented on Feb 26, 2019

    @lastzero
    Member

    @rkkoszewski This is something we want to do, but also not for the start.

  3. added
    low-priorityLow priority due to resource constraints or other reasons
    on May 29, 2019
  4. added and removed
    low-priorityLow priority due to resource constraints or other reasons
    on Dec 30, 2019
  5. lastzero commented on Dec 30, 2019

    @lastzero
    Member

    Related Gitter chat log for future reference:

    Michael Mayer @lastzero 14:26
    For multi user, we basically just need to add a users table to the db... what gets tricky are ACLs, roles and layered permissions - which is what people often mean with "multiple users". This won't be a free enterprise solution.

    Ferdinand Mütsch @N1try 14:26
    What I primarily meant by sharing is to have photo albums that are owned by multiple users (friends, family, ...) and are read + write for all of them. Probably a bigger feature

    Michael Mayer @lastzero 14:27
    I've done all of this for Deutsche Telekom ("Mediencenter") a couple of years ago, so I know what's needed.

    Ferdinand Mütsch @N1try 14:29
    Yep and user registration logic would probably be handy as well. I get your concerns regarding the free enterprise solution problem

    Michael Mayer @lastzero 14:30
    I'm all for making progress and adding cool features, especially sharing will be very important when the foundation is implemented in good quality.

    Ferdinand Mütsch @N1try 14:31
    May I open GitHub feature tickets for multi-user support and shared albums?

    Michael Mayer @lastzero 14:31
    There should be tickets already
    As mentioned, just adding multiple logins is easy but if you don't do it right it can easily end up being a performance and security nightmare
    The database should be able to hold the index in memory which is tricky with many users and much more photos, especially when you start to use sharding. This is not done in one or two days like the login itself.

    Ferdinand Mütsch @N1try 14:37
    I agree...

    Michael Mayer @lastzero 14:39
    So for a family with not as many photos and no security concerns, it can be done later after thoughtfully thinking about the tradeoffs and implications. This needs to be documented very well too with big warning signs.
    However, it would be better for performance to simply run multiple instances and use P2P sharing for albums.
    For this, we might provide a central identity service with unique user name.

  6. renothing commented on Jan 3, 2020

    @renothing

    maybe ActivityPub support is better than multi-user.

  7. lastzero commented on May 17, 2020

    @lastzero
    Member

    @renothing ActivityPub support looks like a great feature for a later release 👍

    Anyone experience with https://github.com/pixelfed/pixelfed?

  8. mcombalia commented on May 18, 2020

    @mcombalia

    I agree just being able to provide multiple login accounts (with the same roles etc) is already a good step forward.

  9. muety commented on Jun 11, 2020

    @muety

    Any news on this? 🙂

  10. lastzero commented on Jun 12, 2020

    @lastzero
    Member

    Working on link sharing next, except you don't create a new account every time you share. You can set a password and expiry date though.

  11. lastzero commented on Jun 12, 2020

    @lastzero
    Member

    We start with albums, but technically you can share everything incl albums, labels, photos and files.

  12. fcimeson commented on Jul 12, 2020

    @fcimeson

    Cloud services such as nextcloud have already solved this problem. On the server the files are all owned by the cloud server and it decides who can view and edit the files.

  13. 285 remaining items

  14. locked as off topic and limited conversation to collaborators on Nov 20, 2022
  15. lastzero commented on Nov 20, 2022

    @lastzero
    Member

    We would like to remind you that this is not a forum and that you can use GitHub Discussions for general questions and comments:

    Thank you! 💖

  16. moved this to Development 🐝 in Roadmap 🚀✨on Jun 8, 2023
  17. added
    sharingSharing with users, anonymously via links or publicly
    on Oct 13, 2024
  18. added
    epicComposed of smaller, releasable features
    and removed
    ideaFeedback wanted / feature request
    on Oct 27, 2024
  19. changed the title [-]Multi-User Photo Gallery with private and shared photos/albums[/-] [+]Sharing: Multi-user / multi-library support with private and shared photos/albums[/+] on Oct 27, 2024
  20. lastzero commented on Oct 27, 2024

    @lastzero
    Member

    I've updated the title of this issue and changed the label to "epic" since initial multi-user support for those sharing a single library was released in 2023, with 2-Factor Authentication and Single Sign-On via OpenID Connect added this year:

    What's still missing to fully satisfy this feature request is the ability to easily set up and index multiple independent libraries on the same instance (so you don't have to set up multiple instances manually), and an improved user interface that makes sharing with other users more convenient and obvious than sending them links to click on:

    Note that in order to avoid duplicate work and merge conflicts, we can only start implementing this once the ongoing upgrade of our frontend component framework is complete:

    This also applies to other frontend-related issues such as batch editing and selecting an album cover image. Thank you very much for your patience and continued support! 🌈💎✨

  21. added
    apiServer API endpoints and documentation
    on May 24, 2025
  22. removed
    epicComposed of smaller, releasable features
    on May 4, 2026
  23. added theissue type on May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

apiServer API endpoints and documentationin-progressSomebody is working on thisprioritySupported by early sponsors or popular demandsharingSharing with users, anonymously via links or publicly

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions