I've done this in the past a bunch of times...you can create a team in another business unit and assign the activities to that team. All of the users can see activities within their business unit (which includes the Corporate Recruiter) but not the ones assigned to the "BLACK OPS" team.
Again, this solution works in case you still need to some activities from the recruiter but not all.
If the users don't need to see the activities of the corporate recruiter at all then I wouldn't create a team and I would just place the recruiter on his/her own Business Unit and adjust security accordingly.
Good Luck!
------------------------------
Gus Gonzalez
8x Microsoft MVP, CRMUG All-Star
CEO, Elev8 Solutions
------------------------------
Original Message:
Sent: Feb 21, 2020 12:47 PM
From: Jennifer Norton
Subject: Confidential Activities
Our Corporate Recruiter is planning to start using D365 to capture his recruiting data and activities. I've set up a section on the Contact form titled Recruiting and added the fields he needs. I'm planning to enable field security on them so only he can see the data entered. The last part I'm struggling with, is how best to allow him to create activities, without allowing everyone else to see them. I've considered modifying the Associated Activities view to exclude his owned records, then creating a separate view for him to use called Recruiting Activities. But I'm worried that users can really just change the Associated Activities view to something else like Closed Activities and then see his records. Is there any way to actually hide his activities from the rest of the company? Maybe put him in a different business unit? Right now all users are in the same one.
Any ideas are welcome!
------------------------------
Jennifer (Norton) Coville
Harden
Jacksonville FL
------------------------------