Microsoft project management software used to plan, manage, and communicate a project schedule and other information among workgroup members, project managers, and other stakeholders.
In Project Professional, the Manage Global Template (or Organizer/Global.mpt) commands are unavailable (grayed out) when the global template is not writable or when access is restricted by policy/permissions.
Typical reasons and what to do:
- Global.mpt is read-only
- If Project is using a Global.mpt file that is read-only (for example, stored in a location where there is no write permission), commands that modify the global template can be disabled.
- In this situation, changes to views, tables, filters, groups, reports, or macros cannot be saved back to that Global.mpt.
- To work with the global template again, ensure Global.mpt is in a folder where there is read/write permission, or save a new Global.mpt in a writable location and point Project to it.
- Enterprise environment (Project Server/Online)
- When using Project Server and an Enterprise Global Template, only users with permission to open and edit the Enterprise Global can modify it.
- If the account does not have those rights, the option to manage the global template can appear disabled.
- An administrator with the appropriate Project Server permissions must open the Enterprise Global from Server Settings, modify it, and save it so changes are available to all users.
- Command disabled by policy/administrator
- Office/Project commands on the ribbon (including template-management commands) can be disabled via Group Policy or other admin controls.
- If this is the case, the command will be visible but grayed out.
- Only an administrator can re-enable it by changing the relevant policy.
If the environment is managed by an organization, contact the administrator or Project Server admin to:
- Confirm whether Global.mpt or the Enterprise Global is locked or read-only.
- Check whether a Group Policy is disabling the Manage Global Template/Organizer command.
- Grant the necessary permissions or adjust the policy so the command becomes available again.
References: