We’re considering implementing groupfolders, but I understand (notably in Discussion: Improving the development process and quality of the app · Issue #1215 · nextcloud/groupfolders · GitHub and 🎯 📚 📕 FAQ ➕ KNOWN ISSUES · Issue #1414 · nextcloud/groupfolders · GitHub) that it is not really advised in production as it contains too many bugs/limitations. I read there (Discussion: Improving the development process and quality of the app · Issue #1215 · nextcloud/groupfolders · GitHub) that an alternative/workaround is to use a “virtual” group.
Would anybody know how to do that and what it means? Notably @pierreozoux ?
Thanks a lot in advance!
Nextcloud version 22
Operating system and version Debian 10
Hello, would anybody be able to direct me in the right direction? Thanks!
Thanks @orandev , I read this:
It’s not a “virtual group”, but a “virtual group user”.
My understanding is that you would create a dedicated user account in your Nextcloud (a user named “groupfolder_project1” for example). Then you would log in as this user in the web interface, create a folder, and share this folder with read/write permissions with the people who are going to use it. You would also need to configure the appropriate quota on this dedicated user account (the same quota you would have set on the group folder).
Maybe there’s something I don’t understand (maybe about the quota?), but why is it necessary to create a specific user? Any user could create this folder and share it with the right permissions. How does it help?
If you wanted a quota on the group folder originally, you can now apply that quota to the user account that shares the folder. You can also delegate administration of a folder by giving the matching user account password to whomever should have it.
If you want the shares to be centrally managed, and don’t care about quotas, you can create a single account to share all the folders. I’d recommend against doing the sharing direct from your admin account, but that’s just on general security principles.