The Editor Config system appears to support a hierarchy of JSON files (similarly to INI files) in three locations:
However, it does not seem to behave correctly in some situations when using more than one JSON file in the config hierarchy.
The customer in this case is trying to use a second "FilterBar.json" file in the project config folder (in addition to the default one in the AppData folder, where the Editor saves the last known state of the Content Browser filters upon closing). The customer's intention is to use this second file to provide team members with a common set of filters to be enabled by default for everyone.
The system works reasonably as expected when opening the Editor, and filters from both json files are merged and applied to the Content Browser (but filters specified in both files disappear from the AppData file, which might be unexpected as well).
Now, when the user adds new filters in the Editor, they get added to the AppData file (not the Project file). On the other hand, when the user removes existing filters from the Editor, which were present in the AppData file, that removal is not persisted anywhere. Next time the editor is opened, the filters are back. This unexpected behavior does not happen if the AppData file is the only one present (no FilterBar.json file in the Project config folder).
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-195274 in the post.