The one thing stopping me from having a "work profile" "private profile" etc, is the permissions.
I could hardlink folders from one user to another, but then there would be permission issues.
I could do a chown -r /home/user/Work
but every newly created file would again belong to "work" and I couldnt edit it with "private" for example.
Libreoffice also doesnt like any permission issues and will only open a copy in those cases.
Would I need an autostart script using pkexec, or a systemd service to always make both users recursively owners of these directories? Is there a better way?
Btw, I use Fedora Kinoite (KDE) and moving things from one user to another takes very long, unlike moving withing the same user. It seems as if it would really change the file location, not just the pointer, but I am no BTRFS expert at all.
Why are you making this so complicated?
Create a shared directory outside of home. Put both users into a group. Make sure that the directory and the files created inside it are owned and writeable by that shared group.
Read up on permissions and ACLs for more on doing this. (I'm being deliberately vague on specifics here because I always seem to fuck up the details here and need to go back to the manuals anyway.)
Home is for your stuff. It is possible to setup sharing of stuff from within home, but there are always going to be more problems with this route because it's designed to be private by default.
You can't hardlink directories. Hardlinking files wouldn't help anyway because each link would get identical permissions. I can't even hardlink at all between home directories on my system because each home directory is a separate filesystem.
Hmm I like Nextcloud and Flatpak apps accessing my files. Not sure about other directoris, but
/var/shared/work
could fit on immutable OSsesWhat does an immutable OS, flatpak, or Nextcloud have to do with basic file permissions between users on the same machine? You still need to learn how basic permissions work with any of those in order to get them working properly anyway.