- 5 hours on-demand video
- 2 articles
- Full lifetime access
- Access on mobile and TV
- Certificate of Completion
Get your team access to 4,000+ top Udemy courses anytime, anywhere.Try Udemy for Business
- Gain an in-depth understanding of the first three knowledge areas of the Advanced Admin Exam Guide - Security and Access, Extending Custom Objects and Apps and Auditing and Monitoring
- Learn Advanced Administrative techniques on the Salesforce Platform in Lightning Experience
- Salesforce Administrator Certification Credential is a Pre-Requisite for the Advanced Admin Certification
We build an Asset Management App in this course.
If you have attained the Salesforce Administrator Certification, you are ready to start the journey to becoming an Advanced Administrator. Become a Salesforce Certified Advanced Administrator by enrolling in this first course of a three-course certification course series. Be sure to get the other two courses as well to complete the set!
I have taught over 110,000 students on the Salesforce platform and I want you to join me in my latest course. I have structured this course to go in-depth on the first three Knowledge Areas of the Salesforce Certified Advanced Administrator Exam Guide:
Security and Access
Extending Custom Objects and Applications
Auditing and Monitoring
The Salesforce Certified Advanced Administrator Certification has a pre-requisite that you have an active Administrator Certification on file - if you have not attained your Administrator Certification, I recommend that you first complete that certification and locate my relevant training courses for that certification via my instructor profile.
We will go in-depth on all of the core concepts and topics of the Salesforce Security Model in this course. It's a deep dive on user accounts, licenses, profiles, permission sets, profiles, roles, groups, teams, territories and more.
This course is recorded in Salesforce Lightning Experience.
And tens of thousands of Udemy Survey ratings for my courses, the students have spoken:
"Are you learning valuable information?" 99.6% answered YES
"Are the explanations of the concepts clear?" 99.8% answered YES
"Is the instructor knowledgeable about the topic?" 99.9% answered YES
- Anyone who has attained the Admin Certification and would like to deepen their skills on the Salesforce Platform
- Anyone needing to learn Territory Management on the Salesforce Platform
- Anyone desiring to attain the Salesforce Advanced Administrator Certification
In this lesson, I provide a high-level overview of the Salesforce Security Model.
Profiles and permission sets provide object-level security by determining what types of data users see and whether they can edit, create, or delete records. For each object, the “View All” and “Modify All” permissions ignore sharing rules and settings, allowing administrators to quickly grant access to records associated with a given object across the organization. These permissions are often preferable alternatives to the “View All Data” and “Modify All Data” administrative permissions.
In this lesson, we look at the relationship between various objects, first referring to the Sales Objects ERD Diagram found within the SOAP API Developer Guide. We then use the Schema Builder to further look at the relationship types between Account, Contract, Contract, Case and Opportunity.
A role hierarchy represents a level of data access that a user or group of users needs. The role hierarchy ensures that managers always have access to the same data as their employees, regardless of the organization-wide default settings. Role hierarchies don't have to match your organization chart exactly. Instead, each role in the hierarchy should represent a level of data access that a user or group of users needs.
In this lesson, I create a criteria-based sharing rule. We specify that any accounts that are named Sony or have a Start Year of 2018 should be shared with the Director, Channel Sales Role and Subordinates. We also create a new ownership-based sharing rule to better fit our scenario and to replace the one we created in the previous lecture. We then adjust an account record to verify that the sharing rule worked as intended.
In this lesson, we go over record ownership and queues.
Every record must be owned by a single user or a queue. The owner has access to the record, based on the Object Settings for the owner’s profile. For example, if the owner’s profile has Createand Read permission on an object, but not Editor Delete permission, the owner can create a record for the object and see the new record. However, the owner won't be able to edit or delete the record. Users higher in a hierarchy (role or territory) inherit the same data access as their subordinates for standard objects. Managers gain as much access as their subordinates. If the subordinate has read-only access, so will the manager. This access applies to records owned by users, as well as records shared with them.
Queues help you prioritize, distribute, and assign records to teams who share workloads. Queue members and users higher in a role hierarchy can access queues from list views and take ownership of records in a queue.
In this lesson, I enable the Account Owner Report. We then run the report while logged in as Jim Doe. I also removed Jim Doe from my Default Account Team and also removed my Role designation on my user account to block access to my records for Jim. This was to demonstrate that although Jim does not have access to my account records and our org wide defaults are set to private on the Account object, Jim is able to see limited details about the accounts in our org, such as account name, owner and last updated date.
In this lesson, we introduce Record Types to the Asset object. We create Record Types for Medical Equipment and Office Equipment. We discuss how Record Types are leveraged to associate Page Layouts by Profile, as well as Picklist Values that are available. In addition, we discuss how Record Types can be assigned on the Profile and a Default Record Type designated.
But we don’t stop there. We look at assigning Record Types by Permission sets. I then share a help article that contrasts the ins and outs of what happens if a user either has the Master Record Type or a Custom Record Type on their Profile and the various combinations of Record Types assigned via Permission Sets.
In this lesson, we explore the use cases and functionality of Delegated Administration. Use delegated administration to assign limited admin privileges to users in your org who aren’t administrators. For example, let’s say you want the Customer Support team manager to manage users in the Support Manager role and all subordinate roles. Create a delegated admin for this purpose so that you can focus on other administration tasks.
In this lesson, we begin creating the underlying foundation for our eventual Asset Management Application. We create a Room custom object via the Schema Builder. Since custom object creation via the Schema Builder does not give you the opportunity to create a Custom Tab for your new Custom Object, we create one and do not associate it with any apps at this point.