Roles and positions both describe people in Fullcast, but they answer different questions. A role defines what someone is accountable for - their function on a territory or team. A position defines who someone is - the title they hold right now, which drives their quota, ramp, and commissions.
The difference at a glance
Roles | Positions | |
|---|---|---|
Question answered | What is this person accountable for on a territory or team? | What title does this person hold right now? |
Examples | Account Executive, Sales Manager, Customer Success Manager | Enterprise AE, Senior Enterprise AE, L1 Senior Enterprise AE, Senior CSM |
How people get one | A coverage assignment places a person with a role on a territory or team | You assign a position with effective dates, individually or in bulk |
Can a person hold more than one at a time? | Yes. Roles can overlap and be active at the same time. | No. One active position at a time. |
What it drives | Territory and team coverage, crediting splits, user permissions, export to your CRM | A target for each person's position, ramp tied to the person, automatic target splits on promotions, comp plan routing |
Permissions | Drives permissioning in the Fullcast system | Does not drive any permissions in the Fullcast system |
Scope | Describes the person's accountability - the part you play on a project, territory, or team, and therefore the outcome you are responsible for on that territory or team. | Describes the person's responsibility and the list of tasks the person must perform, irrespective of the project they are working on. The project, territory, or team you work on has no bearing on your position. |
What roles do
A role is a function, such as Account Executive or Sales Manager. Roles come to life through coverage assignments: a person, in a role, on a territory or team, for a date range. That combination defines who covers what, potentially who gets credit for deals in a territory (depending on the crediting rules), and what appears on the account team in your CRM. Roles also carry Fullcast user permissions, and crediting splits are defined on role assignments.
Because coverage is many-to-many, a person can hold several roles at once - the same rep can be an Account Executive on one territory and an overlay on another.
What positions do
A position is the title a person holds right now. You assign positions to people from the Positions tab of the People Detail view, or in bulk from the Teams grid.
Position history is effective-dated: when a person's position changes, the prior position is end-dated and the new one starts on the change date, so you always know which position a person held on any given day. A person holds one active position at a time.
Targets
Both positions and roles drive targets. You must therefore pick the model you want to use to drive the target.
Topic | Roles | Positions |
|---|---|---|
Outcome | The target is for the role, and can therefore depend on the details of the project, territory, or team the person is accountable for. | The target is for the title the person holds, and is therefore not dependent on any aspect of the project, territory, or team the person works on. |
Subject of the target | A target set by role lets the person who occupies that role inherit the target set on the project. For example, a target can be set on a territory, and the Account Executive on that territory inherits the target while they hold that role, based on their start and end dates in the role. | A target is set on the person in a position. The target is tied to the person in a specific position, so there is no concept of inheriting a target from a project, territory, or team. |
Ramp | Ramp can be assigned to the person in a role on the project or territory. A person can be ramping for each role they are in. Ramp is associated with the role, so if the person changes roles, the ramp does not follow them. | Ramp can be assigned to the person in a position, irrespective of the project they are involved in. Ramp moves with the person if they are reorganized or promoted. |
Rolled up target | Rollups happen at the territory or team level, so a rolled up target can only be inherited by someone in a role on that territory - for example, the manager inherits the rolled up target for all their team members. | Rolled up targets cannot be inherited by a manager in a position. You must explicitly assign a target to the person in the manager position. |
Target survivability | A target can survive a person's association with a territory or team. For example, a target assigned to a territory does not cease to exist when a rep leaves the territory. The target belongs to the territory, so a new rep coming in inherits the territory target. | A target set on a person in a position does not survive the person. When the person leaves, the target ceases to exist. |
Promotions | A person in a role on a territory cannot be promoted and given a new target in the same role on the same territory, team, or product. For example, a person in an AE role who is promoted cannot be given a new target if their role did not change. | A person can be promoted into a new position and given a new target even if their project and manager did not change. For example, a junior rep with a quota of 750K can be promoted to senior rep with a quota of 1M. |
When to use roles
Use roles when the question is about coverage and accountability:
Defining who covers which territory, team, or product
Crediting splits between people on the same territory
Controlling what users can see and do in Fullcast
Exporting assignments to account teams in your CRM
If this is all you need, roles alone are enough. Positions are optional.
When to use positions
Use positions when quota, ramp, or commissions depend on a person's title or tenure rather than on the territories they cover:
People are promoted or change titles mid-period, and commissions must pay each period against the correct quota and comp plan
Quotas differ by title or tenure, and each person's target should follow their position
Ramp should follow the person's position, not their territory coverage
Team-level targets should apply only to people in specific positions
Using both together
Roles and positions are independent attributes of a person, and most organizations that adopt positions use both. Coverage and permissions stay on roles; quota, ramp, and tenure live on positions. Each target reads ramp from exactly one source - position or role. If you have not configured any positions, nothing changes: position columns and tabs do not appear, and your targets and ramp continue to work from roles exactly as before.
Common scenario best practices
Manager quota based on reps rolled up values
Since managers are assigned to the team they manage via coverage, use a role based target. The goal for the role based target should reference the rolled up value of the position based rep target.
Manager quota unrelated to their teams rolled up quota
In the case of managers being assigned a separate quota unassociated with their reps, a role based or a position based target can be used, as both allow for the target to be assigned specifically to a person. Use the "When to use" sections above to determine the best approach for the target.