+1.

At the very least being able to view them and edit them ? Outside of a program that is. I don’t even get why this is how it is. I don’t know what organization could use a system template without the thinnest layer of customisation either…

Asked about this at PAL200 in St Louis, looked again today. Definitely no “edit” options yet.

We’re currently building new templates. Would be great to be able to drop them in the “system” folder, but guess that’s not how we’re meant to use them? 🤔

The only way I can see these system templates being useful is if we were able to create tokenized templates for our CSMs to use, and just pulled those locked templates into those areas as needed -- in areas where we don’t want any edits to be made.

@alizee you can clone a system template & then edit. Also in the new template creation flow user can start from these ready to use  templates and customize accordingly.

@ssamarth, I think this misses the point of this idea. Unless we can customize the templates within the system folder (and add new templates to the system folder so they can’t be accidentally deleted), it’s a waste of space in the menu.

We have a small set of templates we use that we’ve built outside of the system templates folder, and which means we have not one but two template folders in the sidebar.

It should be an easy win to give us the ability to edit and remove those templates as needed.

@alizee you can clone a system template & then edit. Also in the new template creation flow user can start from these ready to use  templates and customize accordingly.

 

@ssamarth honest question: How does making a copy of a system template and editing it, solve the problem of not wanting the system templates available in the first place, because they are not going to be used and just add clutter and confusion?

@bradley i was responding to @alizee query on editing system template 

Fair enough, but I believe the query was about *editing* the system templates. Making a copy and editing the copy is vastly different than editing the thing itself. I don’t think anyone in this thread is concerned about not having enough templates, or an inability to create or modify their own templates. 

What Bradley said: I want to edit them so they are of use. Cloning them will just keep the clutter of system templates on one side, and then “edited system templates” on the other. I just don’t get it. 

​@ssamarth, this is the earlier post I was referencing here re: predefined templates and cloning.

As admins and super asmins, we need the ability, we need the ability to quickly create email templates, often within complex branding requirements. This would solve a great number of issues, including the ask for saved content blocks.

As to this point (cloning a system template and editing) – based on support’s answer that “sometimes cloning templates corrupts the template code” – how does cloning a system template and editing it solve our need to save our own default templates, when if we clone them, we then have to fix issues like broken padding when we’re just trying to send an email?

By having multiple folders of templates called “TEMPLATE”, users may not know which template they need to use, and it’s far more difficult to standardize and enforce brand guidelines for customer emails.

I’m always happy to talk through these ideas regarding the email template builder options. 😀