We have some interns that will be joining us and I want to make sure they cannot see the Case Management object for our client's records. I have one profile that all our program staff (around 90 users) is on that does have visibility to the Case Notes object. I was thinking I would duplicate that profile and just take away access to the Case Notes object and then assign it to the new interns.
Is that the best way to do this? I wanted to ask the hive mind since I know the Salesforce overlords are now deemphasizing profiles.
Alternatively, I could take it off our general program staff profile and create a permission set, add the permission set to my existing users, and then assign it to new users moving forward (barring they're not interns). That seems like a lot of work...
What are your thoughts?
Personally, I would handle this specific task via profiles as you outline, but also take it as an invitation to start a plan to move to permission sets more generally. It's doubtful that just this small change is worth that effort, and it would mean you have this weird outlier where nearly everything is controlled one way, and one function is controlled with a permission set. But this is exactly the kind of use case that is causing the larger move to perm sets, and in my experience once it comes up once it comes again.
So for this set of interns: plot the fastest route to getting them up running with the access you want them to have.
For the future (maybe via the help of an intern): start building a collection of permission sets, in a sandbox, so you can switch over from the profile in the future.
