---
type: concept
title: Nextcloud Group Folders
tags: [nextcloud, collaboration, data-persistence, storage]
related: [nextcloud, ums, ressourcenverantwortliche, resource-folder-lifecycle]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_dienste_webdienste_nextcloud_gruppenordner.md"]
---

# Nextcloud Group Folders

**Nextcloud Group Folders** (Gruppenordner) are collaborative storage directories provided by the URZ that function as institutional resources rather than personal user shares. They are not tied to a specific individual user account and are instead administered as university IT resources.

## Purpose and Persistence
The primary goal of group folders is to ensure that project or research data remains available even if the original creator or a specific member leaves the university. 

### Resource-Based Lifecycle
Unlike standard Nextcloud shares, group folders are managed through the [[ums]] (Account Management System). This ensures that the folder is tied to a "responsible person" (resource owner) rather than a specific user's private storage quota. Persistence is maintained as long as a new [[ressourcenverantwortliche]] (resource owner) is assigned to the resource in the [[ums]], preventing the accidental deletion of project data.

## Administration and Permissions
Because management via the WebGUI is currently technically unavailable, permissions are managed through specific configuration files located within a "Permission" folder.

### Permission Levels
Access is granted via three distinct levels:
- **RO (Read-Only):** Users can view and download files.
- **RW (Read-Write):** Users can read, write, and delete files (full editing and deletion rights).
- **Share:** Users are permitted to share folders and files from within the group folder.

### Permission Logic
- **Highest Right Wins:** If a user is listed in multiple permission files (e.g., both RO and RW), the highest level of access (RW) is applied.
- **Update Delay:** Changes made to the configuration files may take up to **one hour** to propagate within the system.

### Administrative Restrictions
Resource administrators (the responsible persons) have full access by default. To avoid breaking the permission system, the following constraints apply:
- **No Self-Listing:** Admins must **not** add their own names to the permission configuration files, as doing so may cause them to lose the ability to edit permissions.
- **Folder Naming:** The `Permission` folder must remain exactly as named to be recognized by the system.
- **Admin Share Conflict:** Granting an admin "Share" rights via the config files causes the folder to be duplicated in the UI and restricts administrative capabilities.

## Technical Constraints and Integration
- **Folder Structure:** Group folders appear in the root directory of the user's Nextcloud and cannot be moved into the user's own personal folder structure.
- **Nextcloud Client:** Because group folders are technically implemented as **external storage**, they do not synchronize by default in the Nextcloud desktop client. They must be explicitly activated/enabled in the client settings to be synchronized locally.
- **Quota:** Group folders have a default storage quota of **100 GB**, which can be increased upon request.

## Comparison: Group Folders vs. Individual/Standard Shares

| Feature | Group Folders | Individual/Standard Shares |
| :--- | :--- | :--- |
| **Ownership** | Institutional Resource (via [[ums]]) | Tied to a specific individual user account |
| **Persistence** | High / Persistent (if owner is updated) | Low / Expires if creator's account is deactivated |
| **Placement** | Root directory (fixed) | Flexible / Can be placed anywhere in user structure |
| **Management** | Via configuration files | Via WebGUI |
| **Client Setup** | Requires "External Storage" toggle | Automatic sync |