[Bug]: Federated shares can be reshared to teams, but team members can’t access them
Open
Nobody has claimed this yet.
0. Needs triage
32-feedback
bug
feature: federation
feature: sharing
feature: teams
high
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
When you receive a federated share, you can reshare it with teams - but the members of the team don't see the share.
Steps to reproduce
- Share a file or folder with a person or group an another Nextcloud instance.
- As the receiver of the share: Reshare the share via an internal share and see how you can select teams via autocomplete.
- As another member of said team: See how you cannot see the share.
Expected behavior
It should be possible to share with teams (best solution!)
Or, as long as this is not implemented: Teams should not be selectable in the resharing dialog for federated shares.
Nextcloud Server version
32
Operating system
None
PHP engine version
None
Web server
None
Database engine version
None
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
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
No files, tests, or entry points are named. Reproduce the federated-share reshare flow with a team and trace how the share is recorded and exposed to team members; done means members can access it, or teams are excluded from the resharing dialog until support works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, cloud, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100