Dynamic internal setting

[Firesphere]

We have quite a lot of different tasks at the moment (over 80), which are irrelevant to our Q&A team.

While task is useful to them, the list of developer-specific tasks is drowning out the few tasks they need.

I was thinking a .env setting of e.g. dev|test|prod, maybe named TASK_ENV? Which would/could be used to display or hide tasks depending on the relevancy to the user.

It would help keeping the list of available tasks concise for those that don't rebuild binaries on a daily basis, while still retaining those tasks for our dev team.