Add a whitelist in globals.local without messing up default profiles

[pranaovs]

If i am not wrong, using whitelist implicitly means all the other directories in the same depth as the directories are inaccessible, because the particular directory is mount-binded into a sandboxed mount (or something like that).

I want to know how to allow access to a particular folder to all my apps.

Example scenario:

I have ~/tmp directory (yes, in my home) which is a tmpfs mount. I want all my apps to have access to it. When i add whitelist ${HOME}/tmp in my globals.local, i am able to access it from sandboxes like librewolf.
firejail --profile=librewolf --private-bin=ls ls -la ~/tmp

But now few other profiles absolutely break. I think the ones with no whitelist/blacklist in their configs.
firejail --profile=gh ls -la ~ only shows the ~/tmp. But it instead should have access to all (well, atleast not *only tmp) directories in user home.

I can do a read-write ${HOME}/tmp but my librewolf profile cannot access it

I have tried the conditional ?HAS_PRIVATE: whitelist ${HOME}/tmp but it doesn't work and I have no idea what it does.

tldr: allow access to a particular directory in user home but can't use whitelist because it messes up other profiles by making only the whitelisted directory visible

[rusty-snake]

Not possible ATM.

[pranaovs]

Explains so much.

I've been trying off-and-on for the past 4 months but in vain.

I was convinced I was doing something wrong.

Thank you very much

[rusty-snake]

Small XY correction from me:

Add a whitelist in globals.local without messing up default profiles

Not possible

I want to know how to allow access to a particular folder to all my apps.

Almost possible. Because you can add the whitelist to whitelist-common.local.