nextcloud / nextcloud/circles

Resources shared with a team are not available for members that are not the owner

Open
#2,828 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage bug
Dominant language
JavaScript
Stars
177
Forks
68
Avg merge
2d 22h
Merged PRs (30d)
60

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Resources (files/folders) shared with a team are not available for members that are not the owner.


Steps to reproduce
  1. setup fresh Nextcloud installatoin
docker run -it \
--env SERVER_BRANCH=master \
--env CIRCLES_BRANCH=master \
--name nextcloud-easy-test \
--publish 127.0.0.1:8443:443 \
--volume="nextcloud_easy_test_npm_cache_volume:/var/www/.npm" \
ghcr.io/szaimen/nextcloud-easy-test:latest
  1. as bob, create test_team
  2. add john to test_team
  3. share test_folder with test_team
  4. login as john, go to teams page, click on test_team, click on test_folder
Image
  • notice "The file could not be found" on top right popup
Image
  • folder can also not be found under "All files" or "Shared with you" sections for john user
  • running occ files:scan --all did not work to fix this
Expected behaviour

Resources (files/folders) shared with a team are available for members.

Actual behaviour

Resources (files/folders) shared with a team are not available for members.

Server configuration

Web server: Apache/Nginx

Database: MySQL/Maria/SQLite/PostgreSQL

PHP version: 8.5/8.4/8.3

Nextcloud version: 36.0.0 dev

List of activated apps
Enabled:
  - appstore: 3.0.0-dev.0
  - circles: 36.0.0-dev.0
  - cloud_federation_api: 3.0.0-dev.0
  - comments: 3.0.0-dev.0
  - contactsinteraction: 3.0.0-dev.0
  - dashboard: 9.0.0-dev.0
  - dav: 3.0.0-dev.0
  - federatedfilesharing: 3.0.0-dev.0
  - federation: 3.0.0-dev.0
  - files: 4.0.0-dev.0
  - files_reminders: 3.0.0-dev.0
  - files_sharing: 3.0.0-dev.0
  - files_trashbin: 3.0.0-dev.0
  - files_versions: 3.0.0-dev.0
  - lookup_server_connector: 3.0.0-dev.0
  - oauth2: 3.0.0-dev.0
  - profile: 3.0.0-dev.0
  - provisioning_api: 3.0.0-dev.0
  - settings: 3.0.0-dev.0
  - sharebymail: 3.0.0-dev.0
  - sharing: 2.0.0-dev.1
  - systemtags: 3.0.0-dev.0
  - theming: 4.0.0-dev.0
  - twofactor_backupcodes: 3.0.0-dev.0
  - updatenotification: 3.0.0-dev.0
  - user_status: 3.0.0-dev.0
  - weather_status: 3.0.0-dev.0
  - webhook_listeners: 3.0.0-dev.0
  - workflowengine: 4.0.0-dev.0
Disabled:
  - admin_audit: 3.0.0-dev.0
  - encryption: 4.0.0-dev.0
  - files_external: 3.0.0-dev.0
  - testing: 3.0.0-dev.0
  - user_ldap: 3.0.0-dev.0
Nextcloud configuration
If you have access to your command line run e.g.:
sudo -u www-data php occ config:list system
from within your Nextcloud installation folder
Browser

Browser name: Firefox/Chrome/Safari/…

Browser version: 124/125/…

Operating system: Windows/Ubuntu/Mac/…

Browser log
Insert your browser log here, this could for example include:
a) The javascript console log
b) The network log
c) ...

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with the provided Docker setup: create a team as bob, share test_folder with it, and open the Teams page as john. Start by tracing the team resource access and sharing behavior, using occ files:scan --all only as a comparison since it did not resolve the report. Done means john can find and open the shared folder from the team, All files, and Shared with you views.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
authorization, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.