Mission Control - Using Permission Sets to protect Workflow Actions in BC

If a Mission Control Workflow has been configured to control certain actions, such as Releasing a document, it can be desirable to prevent users from manually taking those actions in Business Central.

The best mechanism to limit these actions from happening inside of Business Central is via Permission Sets.

For example, if Releasing a document should only happen via workflow, this action can be prevented inside of BC by creating a permission set that excludes the CODEUNIT 414.   This permission set can then be added to any users which should not be able to take this action inside of Business Central.  The action can still be triggered by the workflow, as the workflow runs with an elevated permission set unaffected by the current users permissions.

Please note that if any other permission set conflicts with this permission set, it may prevent this restriction from functioning properly.  In particular, if the user has the SUPER permission set, they'll always still be able to execute the "Release" action.

Also note that this permission set will not remove the button on the screen, but only prevent the action from being executed.