[Feature Request] Collaborative Collections for multi-user uploads

[miodrage]

Feature Request: Collaborative Collections & Guest Upload Links

🚀 Is your feature request related to a problem?

Currently, slink is great for individual hosting, but it's difficult to collect images from a group of people (e.g., at an event, a wedding, or a team project). Right now, the only way for others to contribute is to share account credentials or have everyone create their own accounts, which is a high-friction barrier.

💡 The Solution

It would be great to see a "Collections" or "Shared Folders" feature that allows for multi-user contributions via a unique link.

Key Features:

• Shared Upload URL: A specific link that allows non-logged-in users (guests) to upload images directly to a specific folder.
• Collection Management: The owner can create, rename, and delete these collections from their dashboard.
• Privacy Controls: * View Permissions: Toggle whether guests can see existing images in the folder or if it's a "blind" upload drop-box.
  • Password Protection: Optional password for the upload link.
• Expiration: The ability to set an expiration date for the upload link (e.g., link expires after 48 hours).

🛠️ Use Case Example

I'm hosting a small meetup. I generate a QR code for a slink collection. Attendees scan it and upload their photos instantly without needing to register an account. All photos are then neatly organized in my "Meetup 2026" folder.

[andrii-kryvoviaz]

Thanks for the detailed and thoughtful feature request! This is something I’d genuinely love to add to Slink.

From an implementation standpoint, I think this can fit nicely into the existing system by introducing share settings and integrating them with the current API (which already supports flexible share extensions). Conceptually, this could live as a new share type for current Collections, something like an Upload Request, that allows contributors to upload with/without needing an account.

I also absolutely love the idea of sharing the upload link via a QR code. That feels like a perfect fit for events and in-person gatherings, and it keeps the whole flow lightweight and accessible.

I can’t promise timelines just yet, but this is very much aligned with where I’d like to take Slink. Thanks again for the great idea and the clear use case.

[lilotter45]

For a slightly different use case - e.g. my wife and I both uploading pictures to the same collection to share with family/grandparents - I think it would be useful to have the ability to assign other users as collaborators, allowing them to see the shared collection in their list of collections.

While I think links are a great idea for events, etc., having to keep track of links to add photos to a longstanding collection could create too much friction for adoption in this scenario.

[andrii-kryvoviaz]

For a slightly different use case - e.g. my wife and I both uploading pictures to the same collection to share with family/grandparents - I think it would be useful to have the ability to assign other users as collaborators, allowing them to see the shared collection in their list of collections.

While I think links are a great idea for events, etc., having to keep track of links to add photos to a longstanding collection could create too much friction for adoption in this scenario.

That’s a great point. It would be helpful to distinguish between your collections and shared collections visible on the collections page (e.g., “Shared with you” vs. “Your collections” filter/label).

I see two complementary sharing modes:

• Upload Request: allows uploads via a shareable link or QR code, with options like expiration, password protection, and anonymous or registered uploads.
• Collaborative Share: allows adding specific users as collaborators. The owner retains control over naming, organization, and deletion, while collaborators can upload new items and manage their own uploads.

One open question is how to handle images uploaded by a collaborator who is later removed, whether those images remain in the collection, revert to the uploader’s private library, or become owner-managed.

By the way, explore page currently serves similar purpose, just it is not categorized.