Method to set system e-mail custom message to not get overridden when republish occurs?
Not as much fun as it should be to see that a person signed up for a newsletter per-say and they got a message all branded with Business Catalyst without you meaning for them to when you've taken the time to set up custom auto-responders and system notification messages. Basically, you just got hosed when that happens. Not only does the form "filler-outer" get a message that isn't branded as the client's with your info on the bottom (co-branded taggin to their audience) but also the client gets the big message that this is all business catalyst; and can use google like any 5 year old to see what the going rates are for monthly SaaS; not what you are marking up to... plus, all the stuff that gets you into the buying funnel like how you can do anything without knowing code... Which at this point I'm cool with... But do not feel like is 100% accurate. It is getting better and paired with Muse, almost to that point. 
So, can I "lock'em down"? - So to speak so I don't have to store the file and remember to replace it, while meanwhile my client is confused about what he's got and a customer didn't get my little mini co-branded add so I think it hurts exposer.
Latest technique I tried, we'll see how it sticks... Put the html that you would have put into the file for system e-mail messages; into a page template and be sure to leave in the {tag=page_content} or it won't save.
Then, just set the system e-mail message to use that template. All the tags for customer name, results and so on should already be in there too; or it won't work. Get that set up; then add it as a template.
If anyone has any other solutions, besides... "don't use muse"... (LOL) Let me know. And if that is what you were going to say I feel you. However, I'm digging it. <--- which def doesn't mean I'm stuck to it.
See TheJacobsonKC.com as a example of muse in BC, with no re-doping the code; just injecting some css and html to the muse file. What muse needs to be so useful to us bc re-branded pawdnas is to have a "set up for bc" option upon publish so that it could be used like a real bc site by the client regarding adding pages, adjusting menus... 
Hell, in the assets menu; if Muse could show the remote server 's customized modules and let you choose which ones to over-ride or not... which would imply that you could also not only design html pages in Muse; but the modules as well and prefer to keep that data; rather than loose it all when you re-publish. Because in Muse; let's face it. You are going to publish a lot.
ps, if you want to see what I'm talking about... check out... thejacobsonkc.com or americanjunkiehb.com (not to get traffic but to illustrate my point of two bc sites created as first tries with Muse.
I'm starting to think.. why fight it? Why not just tell the client to check it out, then tell them they've got the option to edit there? <--- (obviously not for all clients; but some)
Yo- thanks in advance
