Positions
Overview
Positions are the core of how Leadline works. Every applicant, communication, workflow, and report in Leadline ties back to a Position. Whether you call them job postings, opportunities, or requisitions — in Leadline, they are Positions.
A Position is where end users configure everything about a role: the job details, the application form candidates fill out, the landing page they apply through, and the workflow their application moves through. Once published, a Position becomes the engine that captures, processes, communicates with, and reports on every lead generated through your channel tracking links.
This document covers what Positions are, who uses them, when to create them, why they matter, and how to create one.
What are Positions?
A Position in Leadline is an opportunity, job posting, or requisition within your organization that is used to:
- Capture applicant leads generated from your advertising channels
- Process those applicants through a structured hiring workflow
- Communicate with candidates automatically at each stage of the process or manually at any given time as preferred by the end user
- Report on where your best applicants are coming from and how your hiring is performing
Positions can represent a wide variety of openings — a full-time role, a part-time shift, a seasonal position, a contract opportunity, or any other type of requisition your organization needs to fill.
Who Creates Positions?
Positions are created by anyone responsible for sourcing talent to fill open jobs, positions, or requisitions within their organization. This includes — but is not limited to — hiring managers, recruiters, HR administrators, department leads, and operations managers.
Access to create, edit, and manage Positions is determined by your permission level. Permissions are configured by your organization's admin in the Admin Hub.
→ See 124 - User-Roles for more information on user permissions.
If you are unsure whether you have access to create Positions, contact your Leadline administrator.
Who Has Access to Positions?
Company Administrators have full, unrestricted access to the platform and can see all Positions at all times regardless of how they are configured.
All other users will only have visibility into Positions in one of two ways:
- Workflow Assignment — you will see any Position that uses a workflow you are assigned to. This is the primary way most users gain access to Positions in Leadline.
- Collaborator Access — on select Positions, users can be added as a collaborator. This grants access to that specific Position only, regardless of workflow assignment.
If you are unsure why you cannot see a Position or believe your access is incorrect, contact your Leadline administrator.
→ See 124 - User-Roles for more information on user permissions.
→ See 113 - Workflows to learn more about workflows and how your workflow assignment determines Position visibility.
Where Can I View My Positions?
Positions are stored on the Positions page of the platform.
→ See 101 - Platform-Links for the direct link to the Positions page.
→ See 2706 - Apply-Filters-to-Position-View for instructions on applying filters to the Position table to filter Positions by select criteria.
What Filters Can I Use My Positions By?
What are Position Views?
→ See 134 - Position-Views for full product knowledge on Position Views and how they determine what Positions.
→ See 2701 - Create-Position-View for instructions on creating Position Views.
→ See 2702 - Configure-Position-View-Columns for instructions on configuring what columns to display within the Position View.
Where are Positions Created?
Positions can be created in two places:
1. From the Dashboard Click the "Create New Position" button on the main dashboard.
→ See 101 - Platform-Links for the direct link to the Dashboard page.
2. From the Positions Page Click the "Create New Position" button on the Positions page. Both the Dashboard and Positions page launch the same position creation modal — the starting point is the only difference.
→ See 101 - Platform-Links for the direct link to the Positions page.
When Should I Create a Position?
Create a Position any time your organization has an opening it needs to fill. Good indicators that a Position should be created:
- A new role has been approved and needs to be advertised
- A recurring role (e.g. seasonal, high-turnover) needs to be re-opened
- You need to begin collecting and tracking applicants for a specific opportunity
- You want to advertise a role across multiple channels and track which ones perform best
- A previous position was closed but the need has returned
If a previous position was closed but the need has returned or a recurring role needs to be re-opened, it is best practice to create a separate Position for each instance — this keeps applicant data, reporting, and workflows clean and accurate.
If the same role is needed across multiple locations and departments, it is best practice to create a separate Position for each instance as well — this keeps applicant data, reporting, and workflows clean and accurate.
Why Do I Need to Use Positions?
Positions are what make Leadline work. Without a Position, there is no structure to capture applicants, no workflow to process them through, no landing page for them to apply on, and no data to report on.
More specifically, Positions help your organization:
- Fill roles faster — by centralizing everything about an opening in one place and automating candidate communication so no one falls through the cracks
- Reduce turnover — by ensuring the right candidates are being captured, qualified, and moved through a consistent process
- Reduce cost-per-hire — by tracking which channels (job boards, social media, email campaigns, etc.) are generating the best applicants, so you stop spending on what doesn't work
- Scale your hiring — by giving your team a repeatable, structured process that works whether you're filling one role or one hundred
What Apply Experience Options Are Available for a Position?
Every Position must have an apply experience configured. The apply experience is triggered as soon as the Channel Tracking Link is visited by the Candidate. There are three available options, each delivering a different candidate experience:
1. Landing Page
Advertises information about the Position and the organization before the candidate begins the application process.
→ See 109 - Pages for full product knowledge on Landing Pages.
→ See 502 - Assign-Landing-Page for instructions on assigning a Landing Page to a Position.
2. Application Form
Skips the Landing Page entirely, captures the candidate's contact information and consent and directs the candidate directly into the Application Form.
→ See 103 - Application-Form for full product knowledge on Application Forms.
→ See 410 - Assign-Application-Form-Apply-Experience for instructions on configuring this apply experience option.
3. External URL
Skips the Landing Page entirely, captures the candidate's contact information and consent, then skips the Application Form entirely — redirecting the candidate to an external URL instead.
→ See 411 - Configure-External-URL-Apply-Experience for instructions on configuring this apply experience option.
How are Positions Created?
Positions can be created in by using the "Create New Position" button located on the dashboard and on the Positions Page
→ See 401 - Create-Position for creation methods and step-by-step instructions for creating new Positions.
→ See 426 - Create-a-Copy-of-a-Position for instructions on creating a new Position using an existing Position as a template.
→ See 115 - Rover-AI for more information about how Rover AI is used to create positions.
What Can a Position NOT Do?
Positions are the foundation of how Leadline works, but some capabilities belong to other parts of the platform. Here is what a Position does not do on its own:
Positions do not trigger automations. Automations are triggered by the Workflow assigned to a Position. The Position determines what role is being hired for — the Workflow determines what happens to candidates moving through it. → See 113 - Workflows
Positions do not generate submissions. Submissions come from candidates applying through Channel Tracking Links distributed by your team. The Position provides the structure — Channel Tracking Links are what drive candidates to it. → See 106 - Channel-Tracking-Links
What Happens After a Position is Published?
Once a Position is published it is live and ready to start accepting submissions. From here, your team should begin advertising the Position using Channel Tracking Links — these are what drive candidates to your Position and generate submissions.
→ See 106 - Channel-Tracking-Links to get started.
What Fields Make Up a Position?
Positions are broken into three groups: Position Details, Position Settings, and Page Assignment Settings.
Position Details
Required:
- Position Name
- Position Location — currently supports one location per position only
- Brand — the candidate-facing identity assigned to this Position. Selected from a searchable dropdown of your organization's configured Brands. The Default Brand is pre-selected when creating a new Position.
- Job Description
→ See 132 - Brands for full product knowledge on Brands and how they are configured.
→ See 416 - Assign-Brand for instructions on assigning or changing the Brand on a Position.
Optional:
- Salary Type
- Per Hour, Per Day, Per Week, Per Month, Per Year
- Hide Salary Information — hides salary from candidates on the landing page
- Display Salary as a Range — if checked, enter a Min and Max Salary. If unchecked, enter a single Salary value.
- Job Type — Full-Time or Part-Time
- Remote/In-Person — On-site, Fully Remote, or Hybrid
- Position Close Date — includes a close date and close time. The close date can be displayed or hidden on the landing page.
- Requirements
- Benefits
Position Settings
Required:
- Assigned Workflow — the hiring pipeline stages this Position will use
→ See 113 - Workflows for full product knowledge on Workflows and how they are configured.
Optional:
- Collaborators — users granted access to this specific Position outside of their standard Workflow assignment
- Position Tags — may be required depending on how your Company Administrator has configured the platform. Administrators can make Position Tags mandatory to maintain compliance and reporting standards.
- Search Tags — keywords that improve Position discoverability on the Website Widget search bar
→ See 110 - Position-Tags for more information on Position Tags and mandatory tag configuration.
→ See 114 - Search-Tags for more information on Search Tags and how they work on the Website Widget.
Page Assignment Settings
Every Position must have the following assigned before it can go live:
Landing Page Option — one of the following must be selected:
- Application Form — this is the default for all newly created positions. Candidates are directed straight into the Application Form when they click a Channel Tracking Link, skipping the Landing Page advertising experience. If your plan allows, OG Metadata can be customized directly in the Page Assignment tab of the Position Details editor.
- Landing Page — candidates are directed to a branded Landing Page advertising the Position before being prompted to apply.
- External URL — candidates are redirected to an external URL after providing their contact information, bypassing the Landing Page and Application Form entirely.
→ See 109 - Pages for more information on Landing Pages and the available apply experience options.
→ See 501 - Configure-OG-Metadata for instructions on updating OG Metadata for Positions and Landing Pages.
Post-Submission Option — one of the following must be selected:
- Match/Not-a-Match Pages — candidates are redirected to a branded page after submitting their Application Form based on their Lead Score.
- External URL — candidates are redirected to an external URL after submitting their Application Form.
→ See 109 - Pages for more information on Post-Submission Pages and how Match and Not-a-Match Pages are configured.
→ See 119 - Lead-Scores for more information on how Lead Scores determine which Post-Submission Page a candidate sees.
What Happened to the "Employer Name" Field on Positions?
The free text "Employer Name" input that previously existed on Position Details has been replaced by a Brand select input. Users now select a Brand from a searchable dropdown rather than typing a name manually. The selected Brand determines the employer identity displayed to candidates for that Position.
→ See 416 - Assign-Brand for instructions on assigning or changing the Brand on a Position.
What are Collaborators?
Collaborators are users who have been granted access to a specific Position without being assigned to its Workflow. This is useful when a user needs visibility into a select Position or set of Positions outside of their standard Workflow assignment.
This matters because access to candidates in Leadline is tied directly to Position access.
→ See 113 - Workflows to learn more about how Workflow assignments determine access.
→ See 105 - Candidates to learn more about how candidate visibility works across the platform.
What is Position Status?
Position Status is an internal status used to indicate whether a Position is Open, Closed, or Archived within your organization. Position Status has no effect on Channel Tracking Links or applicant flow — it is primarily used for organizational clarity and reporting purposes.
- Open — the Position is active and considered an open requisition within your organization → See 405 - Open-Position for instructions on re-opening a position that was previously marked as closed
- Closed — the Position is no longer considered an active requisition. Leadline records when a Position was closed, enabling your team to run reports against that data. → See 404 - Close-Position for instructions on closing an open position.
- Archived — the Position is no longer active and is hidden from the UI. Archived Positions are always marked as Unpublished and are retained for record keeping purposes only. → See 403 - Archive-Positions for instructions on archiving a position.
Position Status is useful for reporting. For example, you can create a report that shows how many positions were closed in January 2025, how many are currently open across your organization, or how long a position was open before being filled.
→ See 116 - Reporting for more on building position reports.
→ See 409 - Export-Position-Report for instructions on exporting position reports that are unique to a single Position.
What is Published Status?
Published Status controls whether all Channel Tracking Links for a Position are enabled or disabled for applicants.
- Published — All Channel Tracking Links are enabled and accepting submissions.→ See 402 - Publish-Position for instructions on publishing positions
- Unpublished — All Channel Tracking Links are disabled and not accepting submissions at this time. → See 406 - Unpublish-Position for instructions on unpublishing positions.
If you want to disable only specific Channel Tracking Links rather than all at once, you can manage that at the link level.
→ See 106 - Channel-Tracking-Links for more information about how Published Status affects Channel Tracking Links
How Position Status and Published Status Work Together
Position Status and Published Status are independent of each other and can be configured in any combination to fit your hiring needs (with the exception of Archived Positions). For example:
- Closed + Published — the Position is not considered an active open requisition internally, but all Channel Tracking Links remain active and applicants can still apply. This is useful for scenarios where you want to continue accepting applicants without the position counting as an open role in your reporting.
Draft Versions
Positions support draft versioning — meaning changes to a Position are automatically saved as a draft in real time without affecting the live version. You do not need to manually save your work — Leadline saves changes as a draft automatically until you explicitly choose to publish or discard them.
Once you are ready, you have two options:
- Publish Changes — promotes the draft live. Available from the Position details page or within the Position drawer. → See 407 - Publish-Draft-Changes for instructions to publish draft changes for a Position.
- Discard Changes — discards the draft entirely. The Position will no longer be marked as a draft in the Positions table and the live version remains unchanged. → See 408 - Discard-Draft-Changes for instructions on how to discard draft changes to a Position.
The current live version of a Position remains fully active while a draft is pending — it continues accepting submissions and maintains its current Position Status and Published Status until the draft is promoted.
Note: A Position being in draft does not affect its Position Status or Published Status. Open positions remain open and published positions remain published until you explicitly choose to change them.
How do I Configure Position Details?
→ See 414 - Update-Position-Name for instructions on updating the Position Name.
→ See 415 - Update-Location for instructions on updating the Position Location.
→ See 416 - Assign-Brand for instructions on assigning or changing the Brand on a Position.
→ See 417 - Configure-Salary-Information for instructions on configuring Salary Information.
→ See 418 - Create-Job-Description for instructions on creating a Job Description.
→ See 419 - Update-Job-Description for instructions on updating an existing Job Description.
→ See 420 - Configure-Position-Type for instructions on configuring the Position Type.
→ See 421 - Configure-Remote-In-Person-Type for instructions on configuring the Remote/In-Person type.
→ See 422 - Set-Position-Close-Date for instructions on setting a Position Close Date.
→ See 423 - Remove-Position-Close-Date for instructions on removing a Position Close Date.
→ See 424 - Configure-Requirements for instructions on creating requirements for a Position.
→ See 425 - Configure-Benefits for instructions on assigning benefits to a Position.
Related Topics
101 - Platform-Links — Direct links to the Dashboard and Positions page
102 - Admin-Hub — Manage user permissions and access controls
103 - Application-Form — Configure the questions candidates answer when applying
105 - Candidates — Understand how candidate visibility works across the platform
106 - Channel-Tracking-Links — Build, track, and manage advertising links across job boards and campaigns
109 - Pages — Set up and assign branded landing pages to your position
110 - Position-Tags — Configure and manage position tags for compliance and reporting
113 - Workflows — Understand workflows and how assignment determines position and candidate visibility
114 - Search-Tags — Learn about Search Tags and how they differ from Position Tags
115 - Rover-AI — Learn how Rover can assist with position creation and management
116 - Reporting — Build position reports using Position Status and date data
124 - User-Roles — Information about user permissions, roles, and access controls
132 - Brands — Learn about Brands and how they serve as the candidate-facing identity for Positions
401 - Create-Position — All supported methods for creating a position in Leadline
402 - Publish-Position — Instructions for publishing a position
403 - Archive-Positions — Instructions for archiving a position
404 - Close-Position — Instructions for closing an open position
405 - Open-Position — Instructions for re-opening a closed position
406 - Unpublish-Position — Instructions for unpublishing a position
407 - Publish-Draft-Changes — Instructions for publishing draft changes to a position
408 - Discard-Draft-Changes — Instructions for discarding draft changes to a position
409 - Export-Position-Report — Instructions for exporting position reports for a single Position
410 - Assign-Application-Form-Apply-Experience — Instructions for configuring the Application Form apply experience
411 - Configure-External-URL-Apply-Experience — Instructions for configuring the External URL apply experience
2706 - Apply-Filters-to-Position-View — Instructions for filtering Positions by select criteria on the Positions page
414 - Update-Position-Name — Instructions for updating the Position Name
415 - Update-Location — Instructions for updating the Position Location
416 - Assign-Brand — Instructions for assigning or changing the Brand on a Position
417 - Configure-Salary-Information — Instructions for configuring Salary Information
418 - Create-Job-Description — Instructions for creating a Job Description
419 - Update-Job-Description — Instructions for updating an existing Job Description
420 - Configure-Position-Type — Instructions for configuring the Position Type
421 - Configure-Remote-In-Person-Type — Instructions for configuring the Remote/In-Person type
422 - Set-Position-Close-Date — Instructions for setting a Position Close Date
423 - Remove-Position-Close-Date — Instructions for removing a Position Close Date
424 - Configure-Requirements — Instructions for creating requirements for a Position
425 - Configure-Benefits — Instructions for assigning benefits to a Position
426 - Create-a-Copy-of-a-Position — Instructions for creating a new Position using an existing Position as a template
501 - Configure-OG-Metadata — Instructions for updating OG Metadata for Positions and Landing Pages
502 - Assign-Landing-Page — Instructions for assigning a Landing Page to a Position
134 - Position-Views — Learn about Position Views and how they control which Positions are displayed and how they are organized on the Positions page
2701 - Create-Position-View — Instructions for creating a new Position View
2702 - Configure-Position-View-Columns — Instructions for configuring which columns are displayed within a Position View