What must be true for an action to be considered optional in a business case?

For an action to be labeled as optional within a business case, it must not disrupt the primary path. This means that the execution of the optional action should not interfere with the main objectives or workflow of the business case. Optional actions provide additional benefits or enhancements without being critical to the core process. They offer flexibility for users to engage with them when necessary but do not hinder progress if they are not executed.

In contrast, actions that require approval from all stakeholders or are mandatory for all users do not fit the definition of optional, as these conditions create a necessity rather than allowing for choice. Similarly, a restriction that limits performance of the action solely to an admin role also contradicts the essence of being optional, as it imposes a restriction rather than providing a choice. Thus, the focus on not disrupting the primary path is what qualifies an action as truly optional in the context of a business case.