Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page Properties

Target release

Q42024

Epic

Jira Legacy
serverSystem Jira
serverIde9de0c6d-9ef6-3ada-b4ce-7168c44d7e8a
keyTAPSS-2039

Document status

Status
titleDRAFT

Document owner

rommel.ngo

Designer

rommel.ngo

Tech lead

rommel.ngo

Technical writers

rommel.ngo

QA

Sushma Ramachandrappa

...

Excerpt
nameActivities OWD Impact Analysis
  • 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

    TAP Activities - Private (AS IS)

    Only the activity owner (labeled as Assigned To) and users above the activity owner in the role hierarchy can edit and delete the activity.

    TAP Activities - Controlled by Parent (TO BE)

    TAP Users

    A user can perform an action (such as view, edit, transfer, and delete) on an activity based on whether he or she can perform that same action on the records associated with the activity.

    The "parent" of the activity record is:

    • Who Id (Name): Contact and Lead

    • What Id (Related To): Account, Opportunity, Case, Campaign, Asset, and custom objects with Allow Activities enabled.

    TAP Users

    • This limits cross team collaboration.

    • Risk of reduced operational efficiency if data is not visible to teams that need it.

    • visibility of When 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 viewableparented to private objects such as Case, this also still limits cross team collaboration.

    • Potential security concerns since there is no data segregation within TAP

    • As most of our objects are public (Account, Contact, Opportunity), Activities parented to these records are also going to be public which could potetnt

    Non Tap Users

    Cannot see activities owned by TAP users unless they are positioned higher than

    (current or future)

    • No Impact, unless the user is put above TAP users in Role Hierarchy

    • As most of our objects are public such as Accounts, Contacts, and Opportunities, all activities related to these objects inherently becomes public as well where a Non-TAP user could potentially get access to more sensitive information on Activities (i.e. emails, events, tasks, call conversations)

    Proof of Concept : Making Task OWD Sharing to Controlled by Parent,

    ...