Jen Smith - 7 months ago
Much needed. Surely this must be causing client confidentiality and GDPR issues where organisations are unable to restrict access to email conversations for clients and prospects to users in specific profiles/roles? Having access to an account absolutely doesnt mean a user should see all Activities.
Akansha Bansal - 9 months ago
I agree to what is being asked in the original post. Option 'Private' on Activity must behave as completely Private in terms of visibility as well.
This is a bug which is very confusing as per its terminology as well.
Also when Activty is selected as Private and it becomes readonly for users other than Owner, user can still see all edit and delete actions and gets notified of the insufficient access message only after click. The edit and delete actions must be hidden when the record is readonly for a user.
Overall the whole Privacy setting concept on Task is very misleading as we must have it implemented correctly i.e.
Private Activity must be visible only to Owner and people above hiererchy but we should have option to make it completely Private to owner as well.
Anil Malneni - 9 months ago
This is not a feature request. As this is a bug and which needs to be prioratized and fixed ASAP.
We have configured the "Activity" object OWD as Private. however all the users are able to see tasks when they have read-access on related object.
Eschel Hamel - 9 months ago
Per Kayvaan's question (from six years go...):
If you had to choose just one, then I think the first would be preferred over the second.