Deploy a Custom Word Ribbon Without Overwriting the Quick Access Toolbar
Question details
Deploy a shared custom Word Ribbon tab without replacing users' personal Ribbon or Quick Access Toolbar customizations.

- Product
- Microsoft Word
- Device & OS
- not provided
- Scenario
- An organization wants to provide shared Ribbon buttons that run Word macros while keeping individual users' interface settings.
- Observed behavior
- A shared tab is needed alongside personal customizations, and its buttons must call the intended macros.
Identify the macros the shared buttons need to run and confirm that users have desktop Word and permission to run the organization's trusted macros. Use a macro-enabled template for the Ribbon and its callback code, rather than distributing a Word.officeUI file.
Deploy the shared Ribbon in a global Word template
Use RibbonX in a macro-enabled global template to add a shared tab without distributing a file that replaces personal interface settings.
RibbonX defines the tab and buttons in the template. Each macro button needs an onAction callback; a macro that runs from View > Macros will not automatically run from a Ribbon button.
Deploying a separate global template avoids importing a shared Word.officeUI file. The Quick Access Toolbar remains managed separately.
In Word, select File > Save As and choose Word Macro-Enabled Template (*.dotm). Add the intended VBA procedures to the template using the VBA editor.
Close the template in Word, then open the .dotm file in a RibbonX editor. Add a customUI part defining a custom tab and buttons, and give each button an onAction value that names its callback procedure. Save the template.
Open the template's VBA project and add a public callback in a standard module for each onAction value. For example, a button with onAction="RunSharedMacro" can call Public Sub RunSharedMacro(control As IRibbonControl), which in turn calls the intended VBA procedure. Save the template.
Place the .dotm file in each user's Word Startup folder using your organization's deployment method. In Word for Windows, check the location under File > Options > Advanced > File Locations > Startup. Restart Word to load the template.
Open Word, verify that the shared tab appears alongside personal tabs, and click each button. Confirm that macros are permitted by the organization's trust settings and that each callback name matches its button's onAction value.

Keep Quick Access Toolbar settings separate
Use this approach when users need to retain their own Quick Access Toolbar and Ribbon layouts.
Work with Word Documents in WPS Writer
WPS Office is a free, lightweight alternative with a familiar interface for opening and editing Word documents. Its format compatibility helps users move everyday document work across, though it does not fix Word RibbonX deployment.

Frequently Asked Questions
Why shouldn't I distribute Word.officeUI to everyone?
Word.officeUI stores personal interface customizations. Replacing or importing it can overwrite users' existing Ribbon and Quick Access Toolbar settings. Use a RibbonX template for the shared tab instead.
Why does my Ribbon button not run a macro that works from View > Macros?
The Ribbon button needs an onAction value that matches a public VBA callback with the appropriate IRibbonControl parameter. The callback must then call the intended macro.
Where do I install the global template?
Deploy the .dotm file to the user's Word Startup folder. In Word for Windows, find the configured path under File > Options > Advanced > File Locations > Startup, then restart Word.
Can I deploy a shared Quick Access Toolbar without replacing users' settings?
A shared toolbar configuration cannot be transferred to every user without risking replacement of existing settings. Users can manage their own toolbar under File > Options > Quick Access Toolbar.
What should I check if the template loads but its macros are blocked?
Check the organization's macro trust policy and whether the template is signed or stored in an approved trusted location. Avoid enabling all macros as a workaround.




