Public link share for more Users
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Problem / Motivation:
Currently, I can only send one email per link using the external share function.
This creates the problem that I need to generate up to 20 individual links if I want to share with 20 customers.
It is not a proper workaround to create a single link and send it via Outlook/Gmail/etc., because:
My Nextcloud is configured to use a noreply address when sending the share, and it would be a security risk to send both the link and the password from the same email address.
Proposed Solution:
Add an option in the sharing settings to allow entering multiple email addresses at once in the external share field.
For example:
user1@example.com, user2@example.com, user3@example.com
This way, one link can be distributed to multiple recipients directly from Nextcloud without having to create multiple links or rely on external mail clients.
Benefits / Use Cases:
Time saving for users (no need to repeat the same process many times).
Improved security (link and password are still separated and handled by Nextcloud).
Better user experience (no external tools required).
Simple to implement compared to the benefit it brings.
Additional Context:
I believe this is a feature that would benefit many users and should not be too complex to implement.
Please see the attached screenshot for a reference of where this would apply.
Thank you!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the external share field and the existing one-recipient email flow in Nextcloud's sharing settings. Trace how the link and password messages are generated, then verify that multiple entered addresses receive the same link while the separate password-delivery behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- full-stack, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100