I am super excited to let you know that i have passed my salesforce admin certification in just one attempt. When I started this journey, it looked vague to me because i have tried other platforms trying to transition into tech, but holding strong to the assurance from our coach, @Godwin; that he will guide and guard us through the process to actualize our set goal. I had to trust the process with such level of assurance. I gave in my best to make sure i follow every class and video on the PTS platform and the cheat code he gave to me in the form of past questions was the banger, 80% of the content came out. I am here as a testimonial to tell you guys that you can do it too, just key in and trust the process. It is worth it. I am excited it all ended up in success..... See you guys at the top as we grow as a community....

You have just joined a UK based subscription fitness company that sells monthly gym memberships to both individuals and companies. Here is the situation. • One company can have many employees • One employee can have multiple memberships over time • Each membership can include multiple add ons like personal training or classes • Finance wants to report on total membership revenue per company • Operations wants to see active memberships per employee • Sales wants to see which companies have the highest number of active members Right now everything is being stored on Accounts and Opportunities and reporting is completely broken. As the Salesforce Admin, what is the **best data model design** to support this? 🗳️ Vote below and explain your reasoning. This one is intentionally tough and tests real world data modelling thinking 👀 Kind regards Godwin Mbah

Last night, I almost drove myself mad over something that, honestly, I thought I had already mastered. I kept asking myself, “Why can’t this be done using sharing rules?” 😂🤏 The task required creating a Student custom object and controlling who could create, read, update, or delete student records. At first, it felt logical that sharing rules should handle this. However, after revisiting the requirement, it finally clicked that the task was specifically about object-level permissions, not record visibility. That was the moment the formula made sense: PROFILE → Object-level access (Create, Read, Edit, Delete) SHARING RULES → Record-level access (which records users can see or edit) PERMISSION SETS → Additional access layered on top of the profile Once I understood this separation, it became clear why the solution required profiles (Student Manager and Student Viewer) rather than sharing rules. Sharing rules can only extend access to records after object-level permissions have already been granted... they cannot define create, edit, or delete rights. A simple concept, but a powerful reminder that Salesforce security works in layers, and each layer has a distinct role.

whose up?🧐

Can you please let us know the topic we’ll be working on in the next class so we can come prepared? @Godwin Mbah 🙏