What is a macro-enabled template (.dotm and .potm) and when do you need one?
A macro-enabled template is a Word (.dotm) or PowerPoint (.potm) template that carries VBA code alongside its styles and layouts. The macro-free equivalents, .dotx and .potx, cannot store code at all. You need one when the file has to do something, such as building a document from user choices or checking a deck against brand rules.
How do .dotm and .potm differ from .dotx and .potx?
The difference is the letter m, for macro. Both pairs are template files that spawn a new document or presentation when opened, and both carry the same styles, layouts, themes and placeholders. Only the m versions can contain VBA modules, user forms and event code.
The distinction exists so that security software and administrators can treat code-bearing files differently from ordinary ones. An .xlsm workbook, a .docm document and a .potm template are all flagged as containing executable content, and an organisation can allow or block them as a class.
Saving a template that contains macros as .dotx discards the code after a single prompt. This is the most common way custom automation disappears from a corporate template during a routine edit.
What can a macro do inside a template?
VBA in a template automates work staff would otherwise do by hand. The usual examples:
- Populating document properties. A form on opening asks for client name, project number and document status, then writes them into the file properties so every linked field across the cover, header and footer fills at once.
- Inserting approved layouts. A ribbon button drops in a correctly formatted appendix, signature page or pre-styled table without the user touching the Styles pane.
- Running a brand compliance check. A macro scans a deck for off-brand fonts, direct formatting overrides and images below a minimum resolution, then reports what needs fixing.
- Building a document from user choices. A proposal builder asks which sections apply and assembles the document from approved building blocks, in the right order and with the right numbering.
- Cleaning imported content. One button strips pasted formatting, reapplies the correct styles and removes empty paragraphs across a 90-page report.
At Ideaseed this work sits under document automation, and the first question on every brief is whether the outcome can be reached without code.
What do IT and security teams need to approve?
A macro-enabled template needs several things in place before it works reliably at scale.
The first is a trusted location. Macros in files outside a trusted location prompt the user or are blocked outright. Administrators add the templates folder or a specific network path at File > Options > Trust Centre > Trust Centre Settings > Trusted Locations, or by Group Policy for a whole fleet.
The second is a digital signature. Signing the VBA project with a code-signing certificate from the organisation's certificate authority allows the template to run under the stricter setting "Disable all macros except digitally signed macros". Signing also means any tampering with the code invalidates the signature.
Macro behaviour itself is controlled at File > Options > Trust Centre > Trust Centre Settings > Macro Settings. The default, "Disable all macros with notification", shows the yellow Security Warning bar with an Enable Content button. Enterprise and government environments frequently tighten this further, which is exactly why signing and trusted locations matter.
Why does Microsoft block macros from the internet?
Files downloaded from the internet, received as email attachments or opened from some network locations carry a Mark of the Web flag. Office blocks macros in flagged files by default and shows a red banner reading "Microsoft has blocked macros from running because the source of this file is untrusted", with no Enable Content button offered.
The practical consequence is that emailing a .dotm template to staff no longer works. It has to reach them through a trusted location, a SharePoint site added to trusted sites, a software deployment tool or an Organisation Asset Library. An individual user can unblock a single file through Properties in File Explorer, although relying on that across hundreds of people is unworkable.
When is a macro-free template the better choice?
Most of the time. Content controls, building blocks, document property fields and well-built styles handle a large share of what people assume needs code, and they work inside .dotx and .potx files with no security friction at all.
Content controls on the Developer tab provide drop-down lists, date pickers, repeating sections and rich text areas that map to document properties, so a cover page fills itself from a handful of typed entries. Building blocks cover approved content insertion. PowerPoint layouts with the correct placeholders cover most of what an "insert approved slide" macro would do.
Reach for VBA when the requirement genuinely involves logic, such as conditional assembly or validation across an entire document. Everything else is better served by a macro-free template that opens on any device without an IT conversation first.
A .dotm or .potm template is the only way to ship VBA inside a Word or PowerPoint template, and it brings trusted locations and code-signing requirements with it. Macro-free .dotx and .potx templates built on content controls and building blocks solve most template problems without that overhead. Decide which you need before the build starts, because converting afterwards means rebuilding.
To work out whether your template needs automation or simply better structure, get in touch.
Need a branded template? We can turn it around overnight.
Australia's Microsoft Office template specialists with a South Africa team that delivers while you sleep.
RAVE REVIEWS
who we work with
.svg)
.svg)
.svg)
.svg)
