75
Any suggestions/best practices to keep accounts (and possibly opportunities) confidential by assigning a custom "code name" such that only the code name is revealed in the application (depending on security role access, of course) and on reports?
*This post is locked for comments
You may basically need to move all the fields under the security profile, but I'm not sure it's worth it.
One option might be to create a custom field for the actual name and to use out-of-the-box name field to store codes(since you would want those codes to show up in the lookups even when users have no access to the accounts). Although, if your users need to be able to choose an account even when they can't read from that account, I'm not sure how that would work (since, if a user does not have read access to the account, such an account won't show up in the lookup dropdown).
You can set a code, and make the actual account name is a Secured Field. This way only the users that you want to be able to see the real name would be able to.
Hope this helps.
#1
Mohamed Amine Mahmoudi
83
Super User 2025 Season 1
#2
Community Member
52
#3
Victor Onyebuchi
6
Share
Report
All responses (
Answers (
