How to Configure Microsoft Project to Load Global.mpt from Current Folder
Question details
The user wants to configure Microsoft Project Online Desktop Client to load the Global.mpt template file directly from the folder containing the launched MPP file, rather than from the system's default global template location.
- Product
- Microsoft Project Online Desktop Client
- Device & OS
- not provided
- Scenario
- Opening an MPP file directly by double-clicking it from a specific local or network folder.
- Observed behavior
- Microsoft Project ignores any local copy of Global.mpt in the current folder and instead loads the template from its default configured location in the background.
Before modifying how Microsoft Project handles templates, ensure you have backed up your existing Global.mpt file located in your user AppData directory to prevent the accidental loss of custom views, macros, or calendars.
Use the Organizer Instead of Modifying Global.mpt Paths
Since Microsoft Project does not natively support loading Global.mpt from the current working directory, the best practice is to transfer necessary custom elements directly into your project file using the Organizer.
By design, Microsoft Project opens the Global.mpt file in the background from a specific configured location (typically in your user profile's AppData folder) when the application starts. There is no standard setting or configuration that forces Project to use a local Global.mpt file simply by placing it in the same folder as your MPP file.
If you need specific custom views, macros, or formatting for a particular project file to be available to other users, you should use the Organizer tool. This allows you to copy these elements directly into your specific MPP file, embedding them so they travel with the file regardless of the host machine's global template.
Open Microsoft Project and load the specific MPP file that requires the custom views, calendars, or macros.
Navigate to the 'File' tab on the ribbon, select 'Info' from the left menu, and then click the 'Organizer' button.
In the Organizer dialog box, use the tabs (Views, Reports, Modules, etc.) to copy specific elements from your customized 'Global.mpt' (usually on the left side) into your current project file (on the right side).
Close the Organizer and save your MPP file. The custom elements are now embedded within the project file itself, eliminating the need for a local Global.mpt file.
Boost Your Productivity with WPS Office
While Microsoft Project requires complex template configurations for task management, you can handle everyday project tracking, timelines, and reporting seamlessly using WPS Office. It provides a lightweight, highly compatible alternative to Microsoft Office for all your professional document, spreadsheet, and presentation needs.
- 1. Download WPS Office: Visit the official WPS website and click the download button to install the free office suite on your device.
- 2. Open WPS Spreadsheet: Launch WPS Office and select 'Spreadsheet' to start managing your project tasks and timelines.
- 3. Apply Project Templates: Search for 'Gantt' or 'Project' in the template library to instantly create professional, Excel-compatible project tracking sheets.
Frequently Asked Questions
Where is the Global.mpt file located by default in Windows?
The Global.mpt file is typically located in your hidden user AppData folder. The path is generally C:\Users\[YourUsername]\AppData\Roaming\Microsoft\MS Project\[Version]\[LanguageID].
Can I share my custom Global.mpt file with my team members?
Yes, you can share your custom Global.mpt file by having team members replace the default file on their machines with your copy. However, it is usually safer to use the Organizer tool to transfer specific custom views and macros directly into shared MPP files.
What happens if my Global.mpt file is deleted or gets corrupted?
If you delete, rename, or move the Global.mpt file, Microsoft Project will automatically generate a new, fresh default Global.mpt file the next time you launch the application. This is a common troubleshooting step for resolving UI or macro corruption.
