Give Statement Visibility to Team Leads

Learning Objectives

After completing this unit, you’ll be able to:

• Explain how team leads access and work with team members’ statements in Salesforce Spiff.
  
• Configure statement access settings for team leads in Salesforce Spiff.
  
• Compare rollup methods in Salesforce Spiff.
  

Team Member Statement Visibility Through Team Leads

For each team you create, you’re given the option to assign one or more team leads. But what if you don’t have individuals designated as team leads in your org? Team lead is a role in Salesforce Spiff that may not correspond to the same role within your organization. Assigning a user to a team lead role in Salesforce Spiff grants that user visibility (or access) to the team members’ statements. Let's explore this.

What Can a Team Lead See?

When you assign someone as a team lead, when they log in to Salesforce Spiff, they see their own statements and statements for members of their team. This is where maintaining effective dating becomes important. If a team member leaves the team, you likely don’t want the team lead to continue to have access to that team member’s statement. The team lead has access to the statement up until the Effective Until date defined in the team table.

When they click the statement card, the team lead will not be able to recalculate, make a manual adjustment/draw, overwrite, or freeze a statement. Just like the rep themselves, they will only be able to see any metric cards, export the statement, comment on an obligation, open a ticket, or trace calculations.

If you assign more than one team lead to a team, the team leads can’t view each other’s statements unless a team lead is also assigned as a team member.

If one of your users needs access to statements of users on multiple teams, one approach is to add them as a team lead to every team. Or you could create a new team with all of the direct reports they need statement access to assigned as team members. Both of these methods are difficult to maintain. A simpler approach is to take advantage of the Subteams feature.

To accomplish this, first assign the user to be a team lead (no need to assign any team members). Next, click the subteams tab and start adding teams. Then the team lead can see the statements of any members of these teams.

It’s important to know that the team lead in this example only has access to the team members’ statements—not to the statements of the team leads of each of the subteams. If you do need this person to have access to the team leads’ statements, assign them as team members of the parent team.

To assign a team lead, simply click on a team card, then click the team lead button.

Statement Access

There may be situations where you need to determine which plans the lead has access to when viewing their team members’ statements. For example, maybe one or more team members are assigned to more than one plan, but the team lead should only have permission to see the details of one of those plans. Click the team lead’s card to update these settings.

Statement Access defaults to full access, meaning the lead can see statements for all team members and subteam members for all current and future plans.

If partial access is selected, you’re prompted to select the plans the lead has access to. New plans aren’t automatically added to their access permissions. If no plan is selected, the team lead only has access to their own statement. This means that they can’t view their team members’ statements. It’s important to note that this only applies to the team members that are active on their team.

Rollups

The second use case for using teams within Salesforce Spiff is for rollups. These are a common feature of many manager commission plans. They typically refer to revenue (or some other important business metric like gross profit, number of deals closed, and so on) brought in by a team of reps. The manager receives commission on the sum of the revenue closed by the team. In this sense, the revenue that the team closes rolls up to the manager. Some companies refer to plans that use rollups as override plans. Or they might say that a manager receives an override on the performance of their team.

You can manage rollups within your teams in Salesforce Spiff. After your team structures are completed there are a couple of ways to utilize that structure to capture team revenues. Your plans may use one of these methods, both, or even neither.

Assign the Rollup on the Plans Page. This is one of the legacy ways to use the team hierarchies in Salesforce Spiff to create a rollup for your plans in Designer. Designer is the administrative interface of Salesforce Spiff, where Admin and Finance users can create and manage the payout rules used in the platform. It allows users to define and customize how commissions and incentives are calculated and distributed within their organization. Rollups must be turned on under Admin | Settings | Rollups.

Say a team lead earns commission based on the performance of their team. Navigate to Plans, then the plan that the team leader is assigned to. You see a Rollup column on the table. In the dropdown, select the team that the team leader should receive credit for.

Note: This method requires additional logic to be built for the corresponding plan in Designer to complete the rollup process.

Use the Guided Rollup Builder. The Guided Rollup Builder, located in the Data Section of Designer, makes use of the team hierarchies in Salesforce Spiff to create a rollup of team deals. After you create a rollup it’s easy to reference it later on in your plan calculations.

Now that your teams are created and managed in Salesforce Spiff, explore additional features, including custom fields, plan and quota assignment automation, filtering, searching, and exporting.

Resources

• Salesforce Spiff: Rollups: The Basics (login credentials required)