Delegated Administration allows administrators to delegate certain user management tasks to non-administrators. For example, a delegated administrator can assign permissions sets to users in specified roles or public groups without having full access to modify permission sets. References: https://help.salesforce.com/s/articleView?id=sf.admin_usermgt_delegated.htm & type=5

To add a user to an opportunity team, you need Edit access on the account associated with the opportunity and either own the opportunity or be above the owner in the role hierarchy. References: https://help.salesforce.com/s/articleView?id=sf.teams_adding.htm & type=5

Flow is the automation tool that should be configured to utilize the major listing service endpoint. Flow is a tool that allows administrators to automate complex business processes by building flows that can collect, update, or delete data, invoke Apex code, call external services, and more. Flow can use an Apex action or an HTTP request action to send messages to an external endpoint using REST API

Change sets are tools that allow administrators to move customizations such as fields, page layouts, profiles, permission sets, etc. from one Salesforce org to another. To use change sets, administrators need to establish a deployment connection between a source org (such as a sandbox) and a target org (such as production). Then, administrators can create an outbound change set in the source org that contains the components they want to deploy, and upload it to the target org. In the target org, administrators can view and validate the inbound change set before deploying it to their org. References: https://help.salesforce.com/s/articleView?id=sf.changesets.htm & type=5

Permission sets are collections of settings and permissions that give users access to various tools and functions without changing their profile or requiring multiple profiles for users who perform different tasks across apps in your org. By assigning a permission set that has View All on Leads to the contractor, Cloud Kicks can grant them view access to all lead records without modifying their profile or creating a new one. References: https://help.salesforce.com/s/articleView?id=sf.perm_sets_overview.htm & type=5

To grant access for the sales rep who broke their phone and needs multi-factor authentication using Salesforce Authenticator app, the administrator can generate a temporary identity verification code for them. This code allows users who don’t have their verification method available to log in securely without compromising their account security. References: https://help.salesforce.com/s/articleView?id=sf.identity_verification_codes.htm & type=5

A Text Area (Rich) field allows users to format the text with fonts, colors, images, and hyperlinks. It also supports mapping to an opportunity when converting a lead. References: https://help.salesforce.com/s/articleView?id=sf.fields_using_rich_text_area.htm & type=5

Go into the user record and freeze the user is the action that should be taken to ensure the user’s access is immediately revoked. Freezing a user is a way to temporarily prevent a user from logging in to Salesforce without deactivating their user record or changing their profile. Freezing a user can be useful when an employee has resigned or left the company and their access needs to be removed immediately. Freezing a user does not affect the ownership of records or email alerts that are assigned to them

A public group is a grouping of users, roles, roles and subordinates, or other groups that can be used to share access to records or folders. A sharing rule is a rule that grants additional access to records based on certain criteria or ownership. In this case, the administrator should create a public group for the renewals team and create a criteria based sharing rule on opportunities that grants read-only access to the group for all closed won opportunities. This way, the renewals team can see all the opportunities that are eligible for renewal while keeping the account private. References: https://help.salesforce.com/s/articleView?id=sf.admin_sharing.htm & type=5 https://help.salesforce.com/s/articleView?id=sf.sharing_rules.htm & type=5

Making the field Read Only on the page layout prevents users from manually entering or editing the field value on the record page. This ensures that users cannot bypass answering the questions in order to determine their Tier value. Using a screen flow to ask the questions allows administrators to create an interactive user interface that guides users through a series of screens based on their inputs and logic. A screen flow can be used to ask questions and set the field value based on the answers