We’ve been working on our Developer Documentation portal, slowly adding more and more there. It’s a really great resource for Toolkit administration!
Yup, that makes sense. Our Default Config has different settings blocks for different environments - the idea here is that, for example, you typically don’t want artists to inadvertently attach work files to a Project or a Sequence, but you do want to them to attach them to tasks on Asset or Shot pipeline steps. So we don’t include work file templates in the configs for the former, making it so the UI actually won’t let you it the “+New File” button on those.
Another detail to understand is that, as I think you’ve figured out, opening a file via Shotgun->File Open actually changes your context. So, if you’ve launched from Desktop for example, you’re in the project context – Toolkit at that point doesn’t know anything about shots or assets you’re working on. So Workfiles is using the configuration in
config/env/project.yml. If you follow the includes from this file (I can talk you through this if it’s unclear), you’d land at the
settings.tk-multi-workfiles2 block in
config/env/includes/settings/tk-multi-workfiles2.yml, ie, the one you modified.
When you browse to a shot or asset step, then choose a task and either open the existing file or hit “+New File”, as soon as the file loads, your context changes. Your Toolkit configuration in the session is now based on
config/env/asset_step.yml, depending on what you’ve selected. So you’ll want to make sure that those environments (or probably all environments – I don’t see why you would ever not want these filters) have your desired filters.
To do that, again, it comes down to following includes from the environment in question, in order to figure out which block(s) in
config/env/includes/settings/tk-multi-workfiles2.yml you need to change. Honestly, as a shortcut, you could add your filters to all the blocks in that file – might be the easiest way.
Let me know if you have any other questions.