[FEATURE REQUEST] Permission UI handling
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
Permissions can not be increased when content is reshared. In case of a shared folder, all its contents must "inherit" the parent folder permissions.
Currently in Android app, by following these steps:
- User1 shares a folder with User2, granting "share" and "create" permission and revoking "update" and "delete" permissions
- User2 reshares with User3
the current behaviour is:
- By default, shares are created with all permissions granted. To revoke permissions, share must be edited.
- Share from User2 to User3 does not grant any permission by default (only read permission)
- User2 edits his Share with User3. Everything is disabled. If User2 ticks "share" and "create" everything is OK (these are the permissions granted by User1). If User2 ticks "update" or "delete", a snackbar error message is displayed because the permissions are not granted by User1
Describe the solution you'd like
- By default, shares are created with all permissions granted. To revoke permissions, share must be edited.
when a sharee is selected from the list of matches, list of permissions is displayed to be selected by the user to grant the sharee. Permissions by default are ticked/unticked depending values of capability "default_permissions"
- User3 does not have any permission by default (only read permission)
- User3 can tick all the permissions. If that permission is not granted, an alert is shown
Only displayed "create" and "share". "Update" and "delete" are hidden or greyed out.
TASKS
- Research (if needed)
- Create branch feature/feature_name
- Development tasks
- Implement whatever
- ...
- Code review and apply changes requested
- Design test plan
- QA
- Merge branch feature/feature_name into master
PR
- App
- Library (if needed)
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 in the Android app's share and permission UI, then reproduce the User1/User2/User3 folder-sharing steps described in the issue. Trace how the default_permissions capability controls checked permissions and how unavailable permissions are displayed. Done means resharing cannot grant permissions beyond the parent share, and the UI clearly hides or disables those options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100