Deploying MATLAB Customizations Across Organizations and Enterprise Environments: Best Practices and Options

How can I make a company-wide, large-scale, centralized rollout to deploy customizations to all MATLAB users in my organization?

Some use cases could be:

• Adding custom paths (addpath), toolboxes or functions
• Adding MATLAB favorites or shortcuts to the Quick Access Toolbar, for example, to open an internal landing page (R2024b and earlier only)
• Displaying welcome messages in MATLAB Command Window
• Setting default figure properties
• Defining global variables
• Enforcing licensing or usage policies

Answer 1

[MathWorks Support Team]

When you need to enable MATLAB customizations via MATLAB scripts for individual users, there are two common approaches: using a startup script (startup.m) or modifying matlabrc.m. Each method has its own advantages and limitations, and the choice depends on whether you want release-specific, user-specific or system-wide configurations.

Easiest Option: MATLAB Startup Script (startup.m)

The startup.m file is a user-defined script that MATLAB automatically executes every time it starts. It is typically used to configure the MATLAB environment for a specific user or project. This approach is straightforward and compatible across all MATLAB releases.

Advantages: It is easy to implement and modify, and works across all MATLAB versions.

Limitations: Execution cannot be guaranteed (e.g., if multiple startup.m scripts exist on the user’s MATLAB path), and it may override another startup.m that a user has defined.

In terms of where to install the startup.m file for end users, there are two main options for placing it:

1. Custom Directory via MATLABPATH: The most robust method is to place startup.m in a custom directory defined by the MATLABPATH environment variable. MATLAB will include this folder in its search path at startup. This approach can work for all users and installations on the system and allows files to be stored in a centralized, less visible location. However, note that the MATLABPATH variable is not compatible with MATLAB R2016a and earlier on Windows (see here). In addition, this startup.m can be shadowed by a startup.m in the userpath, which is higher on the search path.
2. Userpath Directory: Alternatively, you can place startup.m in the userpath, which is the default folder MATLAB uses for user files (typically %userprofile%\Documents\MATLAB). This method works with older MATLAB versions and does not require administrative rights.The downside is that it must be installed individually for each user, is quite visible (users may modify or delete it), and can be bypassed if the user changes the default userpath.

Advanced Option: Modify matlabrc.m

The matlabrc.m file is a built-in MATLAB script that runs before startup.m as part of MATLAB’s internal startup sequence. It is intended for system-wide configuration and is located in the MATLAB installation directory under <matlabroot>/toolbox/local/matlabrc.m.

Advantages: Guaranteed execution, making it ideal for enforcing organization-wide settings; works for every user on the system; does not override user-defined startup.m scripts.

Limitations: Modifying matlabrc.m requires administrative privileges, must be done for every MATLAB release and installation, and carries the risk of breaking MATLAB if edited incorrectly.