The User Licenses related list in Company Information shows the types of licenses that have been purchased for an org and how many are available or used. It also shows the expiration date of each license type if applicable. This information can help administrators plan for license purchases and manage user access.
Searching for license types in setup does not show how many licenses have been purchased or how many are available or used. User Management settings in setup does not show license information either, but rather settings related to user login, session, identity, etc. Usage-based entitlement related list in company information shows information about usage-based licenses such as API requests or sandboxes, but not user licenses. References:
https://help.salesforce.com/s/articleView?id=sf.users_understanding_license_types.htm&type=5

Guided selling, validation rules, and required fields on the page layout are three options that can be used to ensure sales reps fill out key fields when working on an opportunity through the process. Guided selling allows administrators to add prompts and guidance at each stage of the path to help reps move forward with confidence. Validation rules allow administrators to enforce data quality and business logic by preventing reps from saving records that do not meet certain criteria. Required fields on the page layout allow administrators to make certain fields mandatory for reps to enter before saving records. Configuring opportunity path can help reps visualize and update key fields at each stage, but it does not make them required or prevent them from moving forward without entering them. Using flow to mark fields required is not possible because flows cannot modify page layouts or field properties. References:
https://help.salesforce.com/s/articleView?id=sf.path_guided_selling.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.validation_rules.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.fields_defining_field_properties.htm&type=5

Probability is a standard percentage field on the Opportunity object that indicates how likely an opportunity will close successfully. It is automatically calculated based on the opportunity stage unless you make it editable on page layouts. To allow sales reps to change the probability field value of their opportunities, you need to make the field editable on page layouts. References:
https://help.salesforce.com/s/articleView?id=sf.opportunity_fields.htm&type=5
https://help.salesforce.com/s/articleView?id=sf.customize_layoutedit.htm&type=5

Native debug feature is a tool that can be used to identify the problem with the new flow. Native debug feature allows users to test a flow by running it with different input values and inspecting the output values at each element. Users can also see error messages and warnings that indicate where the flow failed or might fail.
References: https://help.salesforce.com/s/articleView?id=sf.flow_debug.htm&type=5

Minimum password length and password complexity requirement are two settings that administrators can configure to increase the security of user passwords in Salesforce. They determine how long and how complex the passwords must be to meet the security standards. Password different than username and prevent common words are not valid settings in Salesforce, although they are good practices for creating strong passwords.
References: https://help.salesforce.com/s/articleView?id=sf.admin_password_policies.htm&type=5