The principle of 'manage by exception' in PRINCE2 involves setting limits on delegated authority concerning time, cost, quality, scope, risk, and benefits. Here, the aspect of performance that sets limits against the cost of aggregated threats is "Cost". This includes setting tolerances for what can be considered acceptable deviations from the plan before an issue needs to be escalated to a higher authority. Managing by exception helps in efficient use of management time and focuses on deviations that might affect the project's success.
(PRINCE2 7 Foundation Handbook, AXELOS)

Effective issue and change control within a PRINCE2 project relies heavily on a configuration management system. This system tracks all items of the project, including their versions and changes, allowing for controlled changes and ensuring that all items are identified, accounted for, and monitored throughout the project. References: PRINCE2 Foundation official study guide and online resources.

The step where the project manager needs to document how risk management will be undertaken during the project is during the "Identify: define context and objectives" step of the risk management technique. This initial step is crucial for setting the scope and objectives of risk management activities, providing a framework for identifying, assessing, and managing risks throughout the project.
(PRINCE2 7 Foundation Handbook, AXELOS)

In the 'Managing Product Delivery' process of PRINCE2, the team manager's perspective is considered by ensuring that work packages provided by the Project Manager are agreed upon by the Team Manager. This agreement includes understanding the requirements, scope, and criteria of the work packages, thus ensuring that the team manager is fully informed and agrees with what needs to be delivered.
PRINCE2 Foundation Manual