Bug: Share button non-functional for Group Folders in Cubby

[hakunamatata]

Summary

In the Cubby application, clicking the Share button (icon) on any folder located within the Group Folders section does not trigger any action. The sharing modal/UI fails to appear, preventing users from managing permissions or generating links for group-level directories.

Environment:

• OS: macOS Tahoe 26.3 (arm64) / Windows 11 24H2 (x86)
• App: Cubby 2.7.4
• Browser: Safari 26.3 (arm64) and Brave 1.87.188 (arm64) / Brave 1.87.191 (x86)

Steps to Reproduce

• Log into the Cubby instance.
• Navigate to the Group Folders tab on the left-hand sidebar.
• Locate a group folder.
• Click on the Share icon (located on the right side of the folder row).

Expected Result

A sharing dialog should open, allowing the user to add new users or generate a public link.

Actual Result

Nothing happens. No UI element appears.

Additional Notes

Sharing files or folders within My Files or within a Group Folder works, just not sharing the Group Folder itself.

[hakunamatata]

Some other observations:

• How do you delete a Group Folder? I can't see any Delete option in the UI. If I select a Group Folder and press the Delete button on my keyboard, an "are you sure you want to delete" modal pops up but nothing occurs if you select "Yes".
• Currently, to create a Group Folder, you have to click on your Profile and then on Settings. It would be more intuitive if the Add Group Folder button would be in the Group Folders view itself.
• I created a Group Folder but forgot to add any members. Now I have no way to access it. Navigating to https://cubby.domain.tld/#files/groupfolders/slug/ takes you to the Cubby login screen.
• In the Group Folders view, when you click the download button to the right of the search bar results in the following message:

{
 "status": "Not Found",
 "message": "no such groupfolder"
}

[nebulon]

Thanks for the bug reports! I can reproduce the issues around the groupfolders. Looks like a regression when updating dependencies. Fix is coming today.

[nebulon]

The new package has fixed the various bugs around the group folder settings.

Also it hides the currently unsupported actions in the toplevel groupfolder view. (Like download, sharing, ...) We have to see if and how this should be supported for the toplevel groupfolders.

[robi]

@nebulon by using zip of course

[hakunamatata]

For team-based projects with delivery to an external customer, the natural lifecycle of a folder involves two distinct phases:

• Internal Collaboration: The team works together in a shared Group Folder to ensure all members have real-time access to project files.
• Client Delivery: Once a milestone is reached, the team needs to provide the External Customer with a link to that same folder to review the work.

If Group Folders are internal-only, this forces teams to duplicate group folders into "Personal" folders just to share them with a customer.

[hakunamatata]

@nebulon Thanks, just installed 2.7.5 and can confirm that bullet items 1 and 3 from post #2 are fixed.

[nebulon]

I guess that use-case makes sense. I haven't thought of that though. Needs a bit more work, but will keep that in mind. Alternatively currently that external user could be added as a Cloudron user, who only has access to that app, or instead of a group folder, one user could share a folder with everyone involved. However that user is also the owner of the share then (which is not always intended)

[hakunamatata]

That is a possible work around, but does not seem very intuitive in my opinion. If Cubby is intended to be a collaborative file sharing app, it should support sharing of personal and team folders with both internal and external users.

Currently we are using Nextcloud for this. Team Member A, B & C are working together on a project for a customer. Team Member A is to produce document 1, Team Member B document 2, Team Member C document 3. We create a shared folder for Team Members A,B,C and each user uploads their deliverable. Finally we share a link to the shared folder with the customer so that they can review and approve the work.

[robi]

@hakunamatata what does the customer do to to review the work?

As in do they just look at it remotely in cubby or do they download the assets to test locally?

[hakunamatata]

In our particular case (we are an aviation technical services company), say we are performing due diligence on an aircraft that a client is interested in purchasing, the technical person will perform a physical inspection of the asset and subsequently prepare a Pre-Purchase Inspection Report, the commercial person will prepare an Appraisal Report, both of them will collaborate on a Maintenance Cash Flow Forecast and Exposure Report, the legal person will prepare a Title Report among other documents. Eventually all of these documents are shared with the customer. Sometimes they have feedback (e.g. requesting clarification on something, or maybe their financier is requesting something specific to be added into one of the documents) and we may need to amend the report to that effect.

[hakunamatata]

So I guess to answer your question, in our use case, no they would not be making any changes to the files in Cubby. So the ability to share a group folder externally via link with read only permissions would be sufficient for us. But it would be nice to have things like link expiry and password protection.

[robi]

@hakunamatata I see. That's very helpful.

Until cubby is capable, you could accomplish passwords and link expiry by adding Jirefau app to the workflow.

You just need to give it a zip file once customer review is ready.