4. Account Teams (aka Sales Teams)
Thing you’ll definitely need to be familiar with are account teams. And we’ve previously set up account teams in the first course, in this course series for the advanced admin exam and I’m on an account record and under the related tab, one of the related lists is the account teams and you can add a default team to an account or add individual team members.
Now, if you remember, when you add a user to an account team, you’ll specify account role as well. And here are some of the different team roles for the account team. And then as well you’ll set account case and opportunity access and these can vary by team members as well. You see now that our account team is updated to include Jim Doe who is fulfilling the team role of lead qualifier. Now, another thing I wanted to show you while we’re here is if you go into setup and go into your user account, is this often overlooked setting on your user account and that’s your default account team. So if I go into my user account, you see here under the different related list, there’s a default opportunity team and a default account team. If we click on default Account Team, you see that you can associate your default account team to your user record.
So you can add additional members to your account team and set their account opportunity in case access as well as their team role. And so now if we go back to an account, let me go to a different account here and go into the related list, we can add the default team and this will pull up from my user account. And you see here that I added Jim Doe because he is now part of my default team as far as account teams on my user record. So oftentimes account teams are also referred to as sales teams and you can have teams on accounts or opportunities as well.
And these are not to be confused with the hierarchy. Account teams have to do with internal salesforce users that fulfill different roles. So if you go into setup, if you remember from course one of this series and we’ll look for teams here and select account teams, we previously enabled account teams in course one. Now you can disable account teams by clicking here, but then the main links are teams, team roles and replacing team roles. So the team roles are listed here and then you can also deactivate team roles or delete them. You can reorder replace or create new team roles as well.
5. Implementing Paths in the Sales Cloud
Called upon as an advanced administrator to enable paths on various objects in the Sales cloud. And in order to set up a path, you need to search for Path and setup and that brings you to Path settings. If you click on that, you can enable a path by clicking Enable and then select New Path. Now you can set up a path for just about any object in Salesforce now. And so I want to select a Camp as an example of a good object to work with in the Sales cloud. And then as always, you need to give this path a name. And then the main thing to keep in mind when dealing with creating a path is that you can select any pick list on an object. So whatever object that you select will determine which pick lists are available from the list here. So for the campaign object, there’s only one pick list in that status. You can also specify by Record type we have not implemented Record types on the campaign object. So there’s just the Master Record type which is the default. Basically it’s a non record type. All objects in Salesforce have the Master Record type until you implement Record types.
And so you need to bear in mind though, you may be asked on the exam related to paths and the main thing to understand is that that can be set up on any picklist value on an object. So a typical example on Campaigns would be the status field because that is a picklist field on the campaign object. And then the different designations are picklist values for the status field on Campaign are planned, in progress, completed and aborted. Now for a path you can set up different key fields and then also Guidance for Success. And so for the planned status you could add individual fields by selecting them and dragging them over to the selected fields area.
You can add up to five per status designation in this example here. So for example, whenever you’re starting out or early on in the planned status of a campaign, you may want to just have the campaign name and campaign owner. For example, perhaps the description let me go ahead and click Save. And then the Guidance for Success is a WYSIWYG editor and you can provide in context help basically for the end user so that they know what they need to fill in for this status designation. This is a way of providing what are the key fields basically in this status of the campaign in this example.
But it could be for any object, it could be for case, it could be well, I should be careful saying that actually it may not be for every object, but the path is available for some standard objects and any custom object at this time. So whatever object you’re dealing with and once you’ve specified the picklist value that you want to drive this path off of you can then identify the key fields and then the guidance for success. And so as I mentioned, this is a WYSIWYG editor and you can format the text as well. You can insert images, provide links, et cetera.
And so then as you progress, you want to be sure that you select the different picklist values for the status designation here and add additional fields for these different status designations. The idea is once we go from the plan status, the next step in the path would be in progress and then either completed or boarded. So in progress, if we add fields here for an in progress campaign, we may want different fields for the key fields for success. So for example, you may want to specify a parent campaign at this point you may want to specify a start date and type for example. And then for completed you could add fields for a completed campaign. You could specify or have in the path value opportunities and campaign value one opportunities in hierarchy, one opportunities in campaign clicking Save. And if it’s an aborted campaign you may want to include other types of fields such as responses in campaign, converted leads and Campaign.
So click Save and then as well as always, you want to include some guidance for success. I’m just filling in some gibberish here, but in a real world scenario you’d be providing some helpful information. So then once you’re done setting up the different status designations, the key fields and the guidance for success, you want to click next. And this is the finish point of this three step wizard. Then you can set this to Active to make this Active on the campaign object and click Finish. And then once you go to a campaign you will not see this until you’ve adjusted the page layout. So we see here our path that it is active. And so now if we go into campaigns, for example, and select one, we do not see the path in the campaign. So in order to add the path to the page layout we can click on the gear icon and edit page and then this opens up the Lightning App builder and we can edit this particular page. So what we can do is we can select a path and drag it somewhere into the page and then we have our path here. And since we are on the campaign object, it does pull in the one active path that we have available which is the campaign path. So I’m going to go ahead and click Save.
And then once you save you need to activate this to make it visible to users. So I’m going to select Activate and then we want to make this either the default, the app default or the app record type and profile default. So you start off with the base wide, wide default. So this is the base level option as far as orgwide default and then add default. You can assign this as the default for campaign records inside of a specific app. So let’s select the Sales application and click Next and then click Save.
And so then we’ll go ahead and click Save again. It’s here that I never know how often I need to save and at what point I can click back. So if we go to the Sales application, which I have open here, now, you see our path here is enabled on the campaign object and so we can click the down arrow here to see the key fields for this particular status designation and the Guidance for Success. And then if we click on a different status designation, we see the different fields that we set up on the path. So Paths are a very powerful tool that are available on several standard objects and I believe all custom objects will look at that real quickly before we move on to the next lesson.
If I search for Path and we’ll just go through the process of setting up another R1 quickly just to verify what these objects are available for a path. And we don’t have any custom objects, I don’t think. And so these are the standard objects that are available for a path. So this list will grow over time. So if this is a little different in your own instance, just suffice it to say that the same concept holds true. And on the advanced Admin exam, the main thing I think that will probably or likely show up as related to Path has something to do with pick list values. Paths tie into an object, they tie into a record type if you’ve you have them and also most specifically to pick list values and you set up the different fields and Guidance for Success for each pick list value for that particular object and Record type.
6. Customer Scenarios for Territory Management
We worked through part one of this course series for the advanced Administrator exam. You’ll remember through the security knowledge area that we worked our way up, starting with Users and then Orgwide Defaults, all the way up through role hierarchy, sharing rules, manual, sharing, team access, and then finally territory hierarchy access. And then we started to set up territory management as far as setting up territory models, territory settings and then as well territory types. And so, if you remember, and this is inside the Guide to Sharing Architecture, I’ll link to this PDF in the resource section of this lesson. But I feel like it’s important for you to understand some scenarios related to territory hierarchy. And so this is inside of the Guide to Sharing Architecture is they detail some examples of requirements or challenges and then the proposed solution.
Now, these are like gold and these are intended for one of the architect level certifications. But this is going to be very helpful for you to understand territory management and what sort of scenarios this plays into and where it could be useful versus teams as well. This is something that’s very often confused and can get very confusing on the exam. So if you can start to begin to understand the nuance between territory management and teams, whether that be account teams and or opportunity teams, that will be very helpful as well. And as well there’s other scenarios or solutions that require ownership based sharing rules and then as well the role hierarchy.
So these are all key players as far as role hierarchy, sharing rules, teams and territory management that you will see in this diagram here. And so we’re kind of harkening back to what we learned in Security, which was one of the earlier knowledge areas in a previous course in this series it was in course one, but to also start to understand and address some of these scenario based concepts. Now, this is not a demo type of lesson, this is more conceptual. And I do encourage you to take a moment to actually read through the link of these different customer scenarios.
And this should also be in this PDF as well. This is just the HTML version of that same PDF guide to Sharing Architecture and you can download the PDF from here as well. So I wanted to make you aware of this because the exam is very scenario driven and so you may see some of these specific scenarios on the exam. And even if you don’t, this will help you to begin to understand, based on the different requirements and challenges, the proposed solution, and where territory management is the ideal solution. And remember as well that it is at the top of the Sharing Architecture. Inside of Salesforce, everything begins with user and then we work our way up and we open up wider access as we move up this hierarchy here of the Sharing Architecture and Salesforce.
