[Bug]: Share permissions are not properly grayed out if sharee does not have them
Nobody has claimed this yet.
- 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
Since the sharee does not know their permissions, if they reshare with someone else, they are met with an error that is very confusing. Then they have to trial and error their way to create a share with the correct parent permissions.
Additionally, on web and Android, you can see all permissions are enabled even though user3 only has Share permission. When sharing with user2, user3 does not know which permissions they are allowed to enable or disable.
On iOS, you can clearly see which permissions are disabled for resharing:
iOS behavior should be the same on all platforms.
Steps to reproduce
- Be a sharee with limited permissions
- Try to share to someone with full permissions
- Get an error
Expected behavior
Should be properly indicated which permissions you have to reshare
Nextcloud Server version
30
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
Start by reproducing the limited-permission reshare flow from the listed steps, comparing the web and Android permission controls with the iOS behavior shown in the report. Trace the share-permission entry points across the affected platforms. Done means unavailable permissions are visibly disabled and resharing no longer requires trial and error or produces the confusing error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- authorization, frontend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100