Two considerations when installing a managed package in a sandbox are:
* The installation link has to be modified to test.salesforce.com, because the default installation link points to login.salesforce.com which is for production orgs. To install a package in a sandbox org, the administrator has to replace login with test in the installation URL before clicking it.
* The package will be removed any time the sandbox is refreshed, because refreshing a sandbox replaces its current data and metadata with those from its source org. If the source org does not have the package
* installed, then the sandbox will lose it after refresh. Any metadata changes to the package do not have to be recreated in production, because they are preserved during upgrades unless overwritten by the package developer. Install for Admins Only is not the only install option available; there are also Install for All Users and Install for Specific Profiles options. References:
https://help.salesforce.com/s/articleView?id=sf.distribution_installing_packages.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.data_sandbox_implementation_tips.htm&type=5

Flow Builder supports creating a screen that can launch a simple discount calculator when a button is clicked on an opportunity.
References: https://help.salesforce.com/s/articleView?id=sf.flow_builder_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.flow_distribute_button.htm&type=5

Two considerations for preventing users from accessing Salesforce from outside of their network are:
* IP address restrictions are set on the profile or globally for the org, which limit login access based on IP ranges specified by an administrator
* Restrict U2F Security Keys on the user's profile to enforce login hours, which require users to use security keys during certain hours of day Assigning single sign-on to a permission set or enforcing Login IP Ranges on Every Request will not prevent users from accessing Salesforce from outside of their network. References:
https://help.salesforce.com/s/articleView?id=sf.security_networkaccess.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.security_keys_restrict.htm&type=5

To track all cases that reference the new product and give read/write access to the product's two lead engineers, the administrator should create a queue and a criteria-based sharing rule. The queue will allow assigning cases that meet certain criteria, such as having a specific value in the Product field, to a group of users. The criteria-based sharing rule will grant read/write access to the queue members for cases that match the same criteria. References: https://help.salesforce.com/s/articleView?id=sf.queues_overview.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.sharing_criteria.htm&type=5

To surface important values based on stage of opportunity , an administrator should use Path Key fields feature on Opportunity object . This feature allows adding up to five fields that display key information about each stage along path . Users can edit these fields inline without leaving path . For example , an administrator can add Amount , Close Date , Next Step , Probability , and Stage fields as key fields for Opportunity path .
Opportunity Processes , Dynamic Forms , and Workflow Rules are not tools for surfacing important values based on stage of opportunity . References : https :// help . salesforce . com / s / articleView ? id = sf .
lex_path_setup_key_fields . htm & type = 5