Assignments determine coverage for the various aspects of your go-to-market design. People can be allocated to a role for a particular territory, sales team, or product for a specified period of time. Assignments have effective dates, ensuring that the relationships can always be audited for both historical reporting and compensation purposes.
Coverage is defined as the allocation of employees to each aspect of your
Click a node in the hierarchy menu and go to the "Assignments" tab to view the people assigned to that particular territory. You can access the Assignments tab in all designers of the Design Module.
Now, let's understand the elements displayed in the Assignments Tab.
- View Status - In each entry on the assignment page, you'll see a sticker indicating whether the particular employee is Active or Inactive based on the effective dates of the assignment.
- Inheritance - If the person is assigned at a parent node, it will show up in children nodes as "Inherited." Learn more about inheritance here.
- Name of Employee - Each entry in the Assignments Tab will show the person's name.
- Role Assigned - Below the name, you'll see the role assigned to the person. To learn how to assign roles to people, click here.
- Start and End Dates - In each entry, you'll see a quick view of the employees' start and end dates for easy tracking. These show the effective dates at which the association between the person, the role and the go-to-market node they are being assigned to is active.
- Assignment Menu - Click this button to edit, remove, or manage coverage workflows on an assignment in the hierarchy node selected.
- Filter - At the top of the Assignments tab, you can select the assignments you'd like to view using the Filter menu.
- Create a New Assignment - By clicking this button, you'll be able to create a new assignment at the hierarchy node you've selected. More info on this in the section below.
- Ramp Status - The green sprout icon represents that the person in this assignment is ramping. If you roll-over the icon, you'll see a note saying "Ramping".
Assignments made at the parent level carry on to the child nodes, as indicated by the "Inherited" tag. This allows users to allow make assignments for multiple segments or territories at the same time, such as in the case of assigning management or support roles.
Deleting Inherited Nodes
Please note that you cannot delete inherited assignments. If you don't want to inherit an assignment for all child nodes, you will have to assign them individually at each child node instead of assigning it at the parent level and letting it inherit to the children.
Updated about a year ago