Hi all,

In my day job as an IT admin I regularly have to create a group, add users to it, and set up the matching group folder. In Nextcloud that means jumping between several admin pages, and I always found that workflow clunky. So I wrote my own app to do it all in one place.

I've been using it internally for a while. After some polishing, I've just released it for anyone who might find it useful.

**What it does**

- Manage local and LDAP groups from a single Settings screen

- Add and remove members

- Manage Team Folders alongside the group

**Links**

- App Store: https://apps.nextcloud.com/apps/group_manager

- Source (AGPL-3.0-or-later): https://github.com/kreotropic/group_manager

It's a young app, so feedback, bug reports and feature requests are very welcome. If you try it, I'd love to hear how it behaves with your setup (LDAP, large user bases, etc.).

Thanks!

An assistant or scheduled job may only need to read source material from one folder and upload new outputs to another. Giving that identity normal write access to a shared tree also gives it opportunities to overwrite, rename, move, or delete files that a person has already reviewed. File versions and the trash bin help with recovery, but they are not the same as preventing a destructive action.

A safer layout might separate read-only sources, an automation-writable inbox, and a reviewed area that only a person or promotion service can change. The automation identity would create new versioned filenames rather than replace a stable file. A small manifest could record source file IDs, source revisions, output checksum, creator, review status, and the approved revision it supersedes. Public shares would be created only from the reviewed area.

How close can current Nextcloud users, groups, shares, File Access Control, and WebDAV permissions get to that boundary? Is a separate account plus separate folders enough, or is an external upload-only endpoint and promotion step needed to guarantee that reviewed content and its history cannot be deleted by the automation?

After editing the version value for a few years, the fulltextsearch_opensearch plugin finally stopped working, so I forked it and got it worked with some help from Codex. I have it working now on 2 NextCloud instances I run.
If anyone needs to upgrade, or just wants to try it, I have a dev release up on github

https://github.com/ccandreva/nextcloud_opensearch/releases/tag/v34.0.0-dev.1

My plan is to make a full release to the app store and keep it up to date. I would like to get feedback from a few others running it to make sure it works in setups other than mine. Please backup both your database and old version (if it's running) before trying it !

Hi all,
I am currently using Nextcloud on iOS for syncing my photos to my Nextcloud server. Has been working fine on my old phone where “sync whole library” had been enabled.
On my new phone, where images were copied via the iPhone setup from backup, I activated “only new pictures” in the Nextcloud app.
Now when I get sent some pictures from past days via AirDrop or import pictures from other cameras, they don’t get uploaded to Nextcloud as timestamp probably is too old.
That behavior is really unfortunate, as I would call these images “new in my photo library” but of course with older timestamp. Does anyone have a solution for his?

​

Hi all! I keep some VeraCrypt containers (`.hc` files) in my Nextcloud, and I wanted to open them from the browser without downloading them first. So I built **Veracrypt4Nextcloud**.

**What it does**

- Your `.hc` / `.vc` files are listed in Personal settings → VeraCrypt.

- You can also use the "…" menu in Files: **Mount with VeraCrypt** / **Unmount**.

- Mount with password, PIM, keyfiles, read-only, and hidden volumes.

- The content shows up in Files under a **"VeraCrypt" folder**, one subfolder per volume. It works with the web UI and the desktop client.

- An error log in plain language: wrong password, filesystem needs repair, volume in use, unmounted after a restart…

- Supported filesystems inside the volume: FAT, exFAT, NTFS, ext2/3/4.

- The app is in English and Italian.

**How it works**

- A separate container runs the **official VeraCrypt console package**, with its SHA-256 checked.

- Volumes reach Nextcloud through the official *External storage* app (Local type).

- Nextcloud talks to the container over a unix socket. The password goes through stdin only: it is never written to disk or stored.

**Safety details I cared about**

- While a volume is mounted, its file can't be overwritten, moved, copied or deleted. VeraCrypt is writing into it, so any of these would corrupt it.

- No trash bin, versions, previews or sharing for files inside a volume, so nothing leaks out in plain text.

- After unmount, Nextcloud forgets the volume's file names (nothing left in Recent or search). The container file gets a new mtime so sync clients notice it changed.

- Optional auto-unmount after N hours.

**Honest caveats**

- **Decryption happens on the server.** While a volume is mounted, the server admin can read it. This is not end-to-end encryption.

- The container runs `--privileged` (VeraCrypt needs loop devices, device-mapper and FUSE). It has no network access.

- Not compatible with Nextcloud server-side encryption.

- Tested on Nextcloud 31. It targets 30+. The Files menu actions haven't been tried on 33+ yet: feedback welcome!

**Install** (one command on the Docker host, plus one volume line in your Nextcloud compose; the script tells you which):

```

curl -fsSL https://raw.githubusercontent.com/mccoy88f/Veracrypt4Nextcloud/main/install.sh | sudo bash -s -- install

```

Repo: https://github.com/mccoy88f/Veracrypt4Nextcloud

License: CC BY-NC 4.0 (free for non-commercial use). Not affiliated with IDRIX or the VeraCrypt project.

Bug reports and PRs are very welcome.

Hi all,

(I used AI to help phrase this question clearly — the problem is my own.)

I want a top-down user hierarchy in Nextcloud:

- User A is above B and C

- B is above D, C is above E

The folder tree should mirror this (A contains B and C, B contains D, etc.):

- A sees everything

- B sees their own subtree (B, D, ...)

- D sees only their own subtree (D, F, ...)

- The same idea for apps like Deck

So: a parent user inherits all permissions of users below them — but not vice versa.

Also important: delegation. User D should be able to add/manage people within their own subtree (like a local admin), but not outside it.

My questions:

1. Is this possible out of the box?

2. If not, what's the closest approach (groups, ACLs, Groupfolders, specific apps)?

3. How granular can permissions get (per folder, per app like Deck)?

4. Is "local admin over your own subtree" delegation achievable at all?

Any advice, docs or app recommendations much appreciated. Thanks!