@lilly i tried (successfully in the end) to reconfigure some things to make it a multi user setup and everything broke in various ways :) and the docs are garbage and/or unsearchable. try looking up how to add another user the right way
spoiler@lilly unless you don't want everyone to be admin (which is annoying because then you automatically see everyone's documents), you have to set all required permissions by hand. There's no default apart from nothing at all, which is unusable. Then you have to guess / trial and error which ones are needed, because why would the docs tell you which. Or what they even do.
And if you want to have consumption folders per user, you have to do some arcane "workflows" by hand, and there are no docs on how either. Just outdated github discussions. You have to use a trigger for "consumption started" and a path filter for the absolute path of the respective subdirectory of your consumption folder, followed by a slash and asterisk. Then you can do an "assignment" action to assign the document owner. And you have to do this manually for every user.
@j_r It has imo some overspecific service hardening and tmpfiles setup that breaks non-default use cases in hard to debug ways.
e.g. I thought, hey, I'll just set the consumption dir env variable manually so I don't have to disable its tmpfiles settings for it. This made the services restart and fail endlessly with no delay, driving cpu to 100% and making debugging on my not that powerful hardware even more painful.
@fugi oh okay, I probably have a very standard use case then. But yeah very specific service hardening is a thing that I also experienced a few times with other NixOS modules
