Comment 1 for bug 1702929

While this approach would work, and I have no strong objection to it, I'd like to propose a variation that doesn't require that the EG admin mess around with files on the server: store them in the database as JSON blobs, possibly with an OU for scoping which ones to use, and either fetch the desired one when rendering a grid or fetching them en masse during app startup. To create or modify the templates, I further propose that a new column configuration action be added to specify saving the current config to the server.