由管理员配置的文件夹,由组或团队中的所有人共享。 https://GitHub.com/nextcloud-releases/groupfolders
由管理员配置的文件夹,由组或团队中的所有人共享。 https://GitHub.com/nextcloud-releases/groupfolders
Admin configured folders accessible by everyone in a group or team in Nextcloud.
[^1]: The releases are now managed in a dedicated release repository. The releases in this repository may be outdated.
Group folders can be configured through Group folders under Administration settings.
After a folder is created, the admin can give access to the folder to one or more groups, users or Teams (formerly Circles). A quota can be assigned for the folder and advanced permissions can be activated and configured.
Permissions to the content of a group folder can be configured on a per-group/team/user basis.
The configuration options include the Write, Share and Delete permissions for each group.
Once configured, the folders will show up in the home folder for each user in the configured groups or teams.
[!WARNING] There is no record of when a user or team was added to a group folder, and anything related to the team is considered shared knowledge, including previous versions and deleted files.
Team folders are the main storage for teams and have a 1:1 relationship with a team. Their lifecycle and permissions are managed by the team integration, while group folders remain freely configurable by administrators.
Where and how group folder data is stored depends on your Nextcloud instance’s storage configuration.
By default, all files, versions, and trash for each group folder are stored on your server’s local filesystem, inside your Nextcloud datadirectory under a special subdirectory:
/__groupfolders//files/
/__groupfolders//trash/
/__groupfolders//versions/where `` is the numeric ID of the group folder. Each group folder gets its own folder within __groupfolders.
If your Nextcloud instance is configured to use primary object storage (e.g., S3, Swift), all group folder data is stored in the object storage bucket, using the same logical layout as above:
__groupfolders//files/
__groupfolders//trash/
__groupfolders//versions/In this case, data is never stored on the server’s local disk. The mapping and structure in object storage (bucket) mirrors the filesystem layout.
Technical reference:
Group folders always appear as special shared folders in users’ file lists, regardless of whether you are using local or object storage. No additional configuration is needed for accessing or sharing files, regardless of backend storage type.
All access control, configuration, and permissions for group folders are managed within the Nextcloud database and UI as before.
Advanced Permissions allows entitled users to configure permissions inside group folders on a per file and folder basis.
Permissions are configured by setting one or more of "Read", "Write", "Create", "Delete" or "Share" permissions to "allow" or "deny". Any permission not explicitly set will inherit the permissions from the parent folder. If multiple configured advanced permissions for a single file or folder apply for a single user (such as when a user belongs to multiple groups), the "allow" permission will overwrite any "deny" permission. Denied permissions configured for the group folder itself cannot be overwritten to "allow" permissions by the advanced permission rules.
Take a look at this example to understand how to properly configure Advanced Permissions for more complex scenarios with multiple groups or Teams:
Now only users in the "Management" group can write in the sub folder, while all users in the "Employees" group can not.
Note that currently (Nextcloud 31/Hub 10) you need to be a member or admin of a team in order to assign it to a group folder.
All ACL rules always need to have the least permissions for any user/group/Team with access to the sub folder. For those users/groups/Teams that need more permissions you need to add a second rule that grants them the desired permissions.
Users or whole groups can be entitled to set advanced permissions for each group folder separately on the Group folders admin page. For entitlements, only users from those groups are selectable which have to be configured selected in the Groups column.
Some settings are currently only exposed via config/config.php:
'groupfolders.quota.default' => -3,The special value -3 means unlimited and any other value is the quota limit in bytes.
occ)Group folders can be configured and managed from the command-line interface (CLI). This is accomplished by using the occ command.
The occ command is utilized throughout Nextcloud for many operations and is not specific to group folders. When the Group folders app is enabled, the occ command gains additional functionality specific to group folders.
If you're unfamiliar with occ see Using the occ command in the Nextcloud Server Administration Guide for general guidance.
occ groupfolders:create → create a group folderocc groupfolders:delete [-f|--force] → delete a group folder and all its contentsocc groupfolders:expire → trigger file version and trashbin expiration (see Nextcloud docs for versioning and Nextcloud docs for the trash bin for details)occ groupfolders:group [-d|--delete] [write|share|delete] → assign groups and their rights to a group folderocc groupfolders:list → list configured group foldersocc groupfolders:permissions → configure advanced permissions (see below for details)occ groupfolders:quota [|unlimited] → set a quota for a group folderocc groupfolders:rename → rename a group folderocc groupfolders:scan → trigger a filescan for a group folderocc groupfolders:trashbin:cleanup → empty the trashbin of all group foldersocc config:app:set groupfolders enable_encryption --value="true" → activate encryption (server-side) supportoccAdvanced permissions can also be configured through the occ groupfolders:permissions command, but must be enabled first.
Before configuring any advanced permissions you'll first have to enable advanced permissions for the folder using occ groupfolders:permissions --enable. To do this you'll first need to find the folder_id of the group folder you're trying to configure. You can use occ groupfolders:list to find the folder_id of the target folder.
Then you can list all configured permissions trough occ groupfolders:permissions .
occ groupfolders:permissions 1
+------------+--------------+-------------+
| Path | User/Group | Permissions |
+------------+--------------+-------------+
| folder | group: admin | +write |
| folder/sub | user: admin | +share |
| | user: test | -share |
+------------+--------------+-------------+Permissions for files and folders can be set trough occ groupfolders:permissions --group -- to set permissions for a group or occ groupfolders:permissions --user -- to set permissions for a single user.
can be one or more of the following options: `-read`, `+read`, `-write`, `+write`, `-create`, `+create`, `-delete`, `+delete`, `-share` or `+share` to set the set the respective permission to "deny" or "allow". You can delete a rule by passing `clear` as the field.
Note: An advanced permission settings set always needs to be complete (for example +read -create +delete) and not just incremental (for example -create).
Not mentioned options (in the above example that's write and share) are interpreted as inherited.
To help with configuring nested permission rules, you can check the effective permissions a user has for a path using occ groupfolders:permissions --user --test.
To manage the users or groups entitled to set advanced permissions, use occ groupfolders:permissions [[-m|--manage-add] | [-r|--manage-remove]] [[-u|--user ] | [-g|--group ]].
To disable the advanced permissions feature for a group folder, use occ groupfolders:permissions --disable.
See the OpenAPI specification to learn about all available API endpoints: https://petstore.swagger.io/?url=https://raw.githubusercontent.com/nextcloud/groupfolders/master/openapi.json
Group folders are also exposed through a separate WebDAV API at /remote.php/dav/groupfolders/.
In addition to browsing the contents of the group folders, you can also request the mount point for the group folder by requesting the {http://nextcloud.org/ns}mount-point property.
apps folder of your Nextcloud development instance.npm ci to install JS/frontend dependencies.npm run build for a production build or npm run dev for a watch/dev build.暂无开放 Issues,或尚未同步最近议题。