Content Comparison

As we do not know who in the future will be joining Jarvis, it should be noted that they need to actively exclude Non TAP users from ever having access to any TAP Activities. Using Restriction rule have its consideration, one of which is :
Before creating restriction rules, we recommend that you Turn Off Salesforce Classic for Your Org. Salesforce can't guarantee that restriction rules work as intended for end users who are in the Salesforce Classic experience.

🪶Impact Analysis

Excerpt

name	Activities OWD Impact Analysis

	Activities - Private (AS IS)		Activities - Controlled by Parent (TO BE)
TAP Users	Only the owner of the Activity can see their respective Activities. Users who are above of another user in Role Hierarchy can see all Activities owned by users in lower levels	This limits cross team collaboration. Risk of reduced operational efficiency if data is not visible to teams that need it.	visibility of Activities are based on whether the user has access to the parent object of the Activity.	when Activities are parented to a Public object such as Opportunity, Contact and Account, the Activities are viewable Potential security concerns since there is no data segregation within TAP
Non Tap Users	Cannot see activities owned by TAP users unless they are positioned higher than TAP users in Role Hierarchy

...