Relative to: submitter vs. scenario job

once approvals are enabled, you can create your first approval chain there is no limit to how many approval chains you can have, however they will only be utilized if they are assigned as the default chain, or assigned to specific scenario types an approval chain consists of the following submitter person who is submitting the scenario request approver(s) person(s) who will be responsible for approving or rejecting the changes requested fallback approver person who will be placed in the approval chain if the designated approver is no longer in your org if a person is reporting to an open job, their manager's manager will receive the request for approval rather than the open job people notified anyone in your org with access to merge a scenario is allowed to be set as a notified person when an approver is sourced from a person field — for example manager of requester , second level manager of requester , or a custom person field like hiring manager — you can choose whose record that field is read off of the relative to toggle appears beneath the approver source dropdown and offers two options the person submitting the scenario — the field is read off the submitter's own record this is the default and matches previous behavior use this when the approver should be derived from who is filing the request (e g , "the submitter's manager must approve") the job in the scenario — the field is read off the job (or jobs) being changed in the scenario use this when the approver should be derived from the job under review (e g , "the hiring manager on the open req must approve") how multi job scenarios resolve when relative to is set to the job in the scenario if the scenario contains one job , you get one approver if the scenario contains multiple jobs , you get an approver group containing every unique value of the field across those jobs each approver in the group is treated like any other group approver in the chain when the toggle is hidden the relative to toggle only appears for field based approver sources it is hidden when the approver is configured as specific persons — no field lookup is involved, so the toggle is not applicable custom expression — the expression itself already determines what the approver resolves against reading the chain visualizer each stage card in the approval chain visualizer shows a subtitle indicating which mode the approver uses — either relative to submitter or relative to job — so you can confirm at a glance that the chain is configured as intended assigning approval chains once you have approval chain(s) created, you can designate chains to be used on certain types of scenarios created at the top of the setup page, you can set a default approval chain for all scenario types that do not have an approval chain assigned you can make a chain the default chain for specific types of scenarios by checking the box next to your chain, and choosing which scenario types it should be used for this will override your default approval chain for those scenario types packages https //www charthop com/pricing/ headcount planning | compensation planning | hris