Configure one app per department and activate record pages for each app is how the administrator should ensure this is configured correctly. An app is a collection of items that work together to serve a particular function for a group of users. An app can include items such as tabs, objects, reports, dashboards, and record pages. A record page is a type of Lightning page that displays details about a specific record. A record page can be customized using Lightning App Builder and activated for different apps, profiles, or record types. By configuring one app per department and activating record pages for each app, the administrator can ensure that the backup team users can view records in a way that makes sense for each department depending on which app they are using.

To access a junction object record, a user needs to have at least read permission on one of its master records and on the junction object itself. If the user does not have access to either master record, they cannot access the junction object record. If the user has access to both master records, they can access the junction object record with the most permissive access level of either master record. Reference: https://help.salesforce.com/s/articleView?id=sf.security_sharing_rules_types.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.relationships_manytomany.htm&type=5

An entitlement is a record that represents a customer's right to receive support or service based on the terms of a contract or agreement. An asset is a record that represents a product that a customer has purchased. To automatically provide phone support to customers who purchase photo editing software, the administrator can create a flow that attaches an entitlement to the asset upon purchase. The entitlement can have a term of 365 days and a service contract that specifies the phone support details. Reference: https://help.salesforce.com/s/articleView?id=sf.entitlements_overview.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.assets_overview.htm&type=5

Dynamic actions are a way to conditionally display actions on a record page based on criteria such as field values, user profile, device type, or record type. Dynamic actions can help streamline the user interface and guide users to take the right actions at the right time. Dynamic actions can be used to show or hide the Create Contract button based on the opportunity stage value