Just Eat Takeaway.com’s Post

In this guide, we delve deep into the nuances of Salesforce's record level security. We'll explore concepts like Organization-Wide Defaults (OWD), the significance of record ownership, and how the role hierarchy can influence data visibility. This also includes a Demo: -Setting OWD to Private -Creating Role hierarchy -Assigning Users to Roles -Checking visibility -Changing Record Owner -Checking visibility for Owner and Roles above. This video is in the Salesforce Security Spectacular. https://lnkd.in/djw3tdQ9

This feature alone will pay back instantly. I can’t tell you the amount of times I’ve been asked in the last 10 years for this level of insight into post deployment permissions #ElementsCloud the #ChangeIntelligencePlatform #compliancematters #zerotrust

I am following up for my previous video about how Apex Sharing on Account are removed on Owner Change because the only sharing reason you can use is Manual, this came up in teaching the "Sharing And Visibility Architect" class. Here is an alternative approach. You can create Territories and use them as targets for you Apex (Programatic) Sharing. You add Accounts dynamically, and you add Users dynamically. This does limit you to using Territories as "buckets" and you may limited to 1000 Territories, unless you request more. However, if your custom model supports this bucket approach, it could work for you. This video is in the Salesforce Security Spectacular. Salesforce Salesforce Architects #salesforce #architect #security #sharing https://lnkd.in/g2DxjArj

Flow Like a Developer Trust but verify I can't tell you how much wrong information there is out there. In the past week, I've seen blatant misinformation about security, data models, flow, and Apex. And the engagement with these posts is high. Read it, but be skeptical. Ask probing follow-up questions. Follow up with independent research to confirm. Notice other comments on the post; do they agree? Heck, don't believe everything I post. I'm a human; sometimes, I make mistakes. --- Salesforce Professionals and Organizations have a lot to deal with already. Can we reduce the amount of bad information floating around? #salesforce #flowlikeadeveloper #flow #salesforceflow

Stay in the loop, with our latest product updates. Rick Roesler, our Senior Technical Product Manager, has written "Permissions Explorer: a game-changer in Salesforce Permissions management" - a guide to our innovative suite. Inside this blog, you'll discover how Permissions Explorer offers: - Streamlined Management & Precision - Enhanced Security & Compliance - Efficient Profile Consolidation - Actionable Insights & Reporting Read our blog to explore further! https://hubs.ly/Q02fB-hn0 #PermissionsManagement #DataSecurity #SalesforceTips #ITSecurity #AwesomeAdmins #Profiles #PermissionSets #Salesforce

🔥 Excited to Announce a New Achievement! 🔥 Thrilled to share that I've successfully completed the Integration Security Specialist Superbadge! 🚀🌟 It took several hours of dedicated effort, but it was worth it. This Superbadge is designed to validate expertise in integration best practices and the configuration of named credentials. The Integration Security Specialist Superbadge consists of two units:  1.Integration Configuration Superbadge Unit  2.Named Credentials Superbadge Unit In the Integration Configuration unit, I: >Set up an integration user >Established a JWT Bearer flow connected app >Defined an OAuth custom scope >Configured a connected app to use OpenID Connect >Configured an Auth. Provider with OpenID Connect In the Named Credentials unit, I: >Securely stored external credentials >Configured named credentials to make callouts The last step was particularly challenging! However, the experience was incredibly rewarding. One suggestion for Salesforce Trailhead: the descriptions could be more detailed. It would certainly help future badge earners. #Salesforce #Superbadge #IntegrationConfigurationSuperbadgeUnit #NamedCredentialsSuperbadgeUnit #SalesforceDevelopers #IntegrationSecuritySpecialistSuperbadge #Integration #Trailhead

This blog post by Samantha Shain delves into the complexities of troubleshooting and resolving error messages within #Salesforce, notoriously the "Insufficient access rights on cross-reference id" error. Samantha shares her personal experiences and challenges in navigating various scenarios where this error occurred, ranging from email sending in flows to issues encountered by Partner Community Users creating records. Throughout the post, she emphasizes the importance of understanding the underlying causes of such errors in Salesforce and offers insights on effective problem-solving techniques. https://shorturl.at/duwHV

🔔 Salesforce's Continued Innovation in Permissions & Profiles: A Deep Dive into the Winter '24 Release 🌟 Big news for Salesforce enthusiasts! As you may know, Salesforce has postponed the End of Life for Permissions on Profiles originally slated for Spring '26. But that's not the end of the story. 💡 Innovation Continues: Despite the pause, Salesforce remains committed to innovating in the permissions and profiles domain. The Winter '24 release introduces a game-changing feature: the "View Summary (Beta)" button on the permissions set layout. 🔍 Why It Matters: This new button is a significant leap forward. It doesn't just display basic information about the permission set (like Created By, License, Description, and Namespace Prefix) but goes a step further. It clearly outlines what the permission set actually permits. This is a huge time-saver and efficiency booster. 👀 Ease of Use: Previously, understanding permissions involved tedious checking of individual permissions or exporting and analyzing CSV/XML data. Now, Salesforce offers this information in a straightforward, user-friendly UI. 🚀 What's Included in the Summary: • Groups: Which permission set groups include the perm set • Permissions: Details on User and System Permissions • Access Levels: Comprehensive CRUD access on Objects and Fields, and access to External Credentials 🔐 Implications for Security Architecture: This update is particularly crucial for teams looking to overhaul their permission sets and shift from a profile-driven to a permission set-driven security model. 🌐 A Step Towards Modernization: This enhancement is a clear indicator of Salesforce's commitment to modernizing key areas of its platform. I'm excited to see what's next! 👥 Community Thoughts? How do you see this impacting your Salesforce use? Is moving to a permission set-driven security model on your roadmap for 2024? Let's discuss below! #Salesforce #Winter24Release #CRM #Innovation #PermissionsManagement #UserInterface #SalesforceCommunity

Beware of generic code quality tools in #Salesforce #DevOps! They may save you money up front, but lack coverage for important issues leading to missed errors and unreliable reports. Opting for specialized solutions supports a successful security strategy. Remember: Quality can't be beat! 🖥️🛡️ Our blog digs into 8️⃣ things you’ll get by using a generic code quality tool in Salesforce ⬇️ ▶ Irrelevant information that obscures findings ▶ Minimal Salesforce coverage ▶ Unhelpful focus on CVE/CVSS scores ▶ Difficult integrations across components ... ⬇️ Learn more: https://bit.ly/43Bnpvk

🚀 Day 6 of the Trailhead Challenge: Privileged User Responsibilities 👩💻Today, I completed the Privileged User Responsibilities module, delving into the crucial concepts of privileged access and privileged access management (PAM). Understanding the significance of setting access control limits and the security challenges involved was eye-opening. Excited to continue my journey and apply these principles to bolster security measures! 💡 #TrailheadChallenge #PriviledgedUserResponsibilities #SalesforceSecurity 🔐 #ContinuousLearning #salesforceAdmin #Salesforce #TrailblazerCommunity #SalesforceBA #SalesforceTraining #TrailheadQuest #30daysTrailheadChallenge #30dayschallenge #Trailhead