Currently, when you "Lock the project for viewing," the macros also disappear from the Macro List. This means you cannot prevent users from editing the code while still allowing them to quickly run the macro from the list (similar to how Excel handles this).

As confirmed with Bentley support, this behavior is working as designed, so it seems we should retain the current functionality.

However, I imagine a more user-friendly approach to this issue. For example, we can already hide a module from the list using "Option Private Module". Introducing options like "Option Show Macro" and "Option Hide Macro" could provide more control by allowing protected macros to appear in the list or hiding unprotected macros as needed.

I understand this change does not enhance macro security—"Locking the project for viewing" already offers limited protection. However, it would provide a smoother way to control access to macro code and functionality.

While customizing the ribbon to add a special icon for running hidden macros is a workaround, I believe the proposed solution would strongly support current functionality.

Regards!