Version Control Strategy for Level User Settings

My current cinematic project requires the use of a custom BP_UserSettings actor class that controls the behaviour of other actors in the level (In Editor, PIE and MRQ modes). This BP_UserSettings can be customized by each team member.

Should I put this BP_UserSettings actor inside a dev sub-level and ignore this map (ie: *_Dev.umap) from version control? Is this the right approach?

BTW I don’t think editor blueprints are suitable because I also need to access these user variables in PIE and MovieRenderQueue.