• Enable Tiered Office Display: Toggle between hierarchical tree structure or flat alphabetical list
  • Enabled: Offices shown in parent-child tree structure with indentation
  • Disabled: Offices shown as a simple alphabetical list
• Maximum Hierarchy Depth: Control how many levels of hierarchy to display
  • 0 (Unlimited): Show all levels (State → City → Office → etc.)
  • 1: Show only top level (e.g., States only)
  • 2: Show two levels (e.g., States + Cities)
  • 3: Show three levels (e.g., States + Cities + Offices)

• .irongforce-hierarchical-select-container – Main container for hierarchical select
• .irongforce-select-depth-0 – Root level items (bold, light background)
• .irongforce-select-depth-1 – First child level (indented)
• .irongforce-select-depth-2 – Second child level (more indented)
• .irongforce-select-depth-3 – Third child level
• .irongforce-select-depth-4 – Fourth child level
• .irongforce-select-depth-5 – Fifth child level
• .irongforce-select-parent – Any item that has children
• .irongforce-select-child – Items without children

• Companies with offices in multiple states/regions
• Organizations with complex geographic structures
• Job boards where location filtering is important
• Sites that want to reduce dropdown clutter with logical groupings

• Sidebar Display: Featured jobs appear in a dedicated sidebar next to the main job listings
• Layout Classes: The main container gets has-featured-jobs class when featured jobs exist
• Responsive Design: Sidebar collapses on mobile devices (991px and below)

• .irongforce-layout-wrapper.has-featured-jobs – Main container with featured jobs
• .irongforce-featured-jobs – Featured jobs sidebar container
• .irongforce-featured-jobs-list – List of featured jobs
• .irongforce-featured-job – Individual featured job item
• .irongforce-featured-job-title – Featured job title
• .irongforce-featured-job-meta – Featured job metadata container
• .irongforce-featured-job-department – Department information
• .irongforce-featured-job-location – Location information
• .irongforce-featured-job-time – Employment type
• .irongforce-featured-job-date – Job posting date

• Change any text, labels, or messages that appear on your job listings
• Supports multiple languages or custom terminology
• Changes persist through plugin updates

1. Directory Setup: Create the directory /wp-content/irongforce-translations/ in your WordPress installation
2. Translation Files: Create JSON files with the naming convention:
   • irongforce-{job-board-token}-translations.json
   • Example: irongforce-mycompany-translations.json
   • Note: Special characters in your token (hyphens, spaces, etc.) are replaced with underscores. For example, token my-company uses filename irongforce-my_company-translations.json
3. File Permissions: Ensure the web server can read the files (644 permissions)
4. Automatic Loading: Files are automatically loaded based on your job board configuration

{
  "departments": {
    "Engineering": "Tech Team",
    "Sales": "Revenue Team"
  },
  "locations": {
    "New York, NY": "NYC Office",
    "Remote": "Work from Home"
  },
  "metadata": {
    "employment_type": {
      "Full-time": "Full Time Position",
      "Contract": "Contractor Role"
    },
    "job_function_2": {
      "Backend Development": "Server-side Engineering"
    }
  }
}

• departments – Department/team names from Greenhouse
• locations – Office locations and geographic data
• metadata – Custom fields from Greenhouse including:
  • employment_type – Full-time, Part-time, Contract, etc.
  • job_function_2 – Specific job function categories
  • Any other custom metadata fields from your Greenhouse setup

Need assistance with setup or additional override keys? Contact our support team for guidance.

• Custom search redirect functionality
• Dynamic filters that appear based on available job data
• Advanced location and department filtering
• Keyword search across job titles and descriptions
• Attribution-safe query parameter forwarding across search, job detail, and application flows

• Creates a search form that redirects to your main job listings page
• Maintains search terms and applies them automatically
• Preserves existing tracking parameters such as gh_jid, gh_src, source, ccuid, and UTM tags
• Useful for homepage or landing page search boxes
• Requires: A target page with the main job listings shortcode

Search Form Page:

[irongforce_search_redirect job_board="your-token" redirect_page="/careers/"]

Results Page:

[irongforce job_board="your-token"]

Example URL after redirect:

yoursite.com/careers/?keys=engineer&teams=Engineering&location=New+York

• keys – Keyword search terms
• teams – Department/team filter
• location – Location filter
• meta_location_only – Meta location filter
• job_function_2 – Job function filter
• gh_jid – Greenhouse job ID for direct job routing
• gh_src and source – Source attribution values
• ccuid – Greenhouse candidate context identifier
• utm_source, utm_medium, utm_campaign, utm_term, and utm_content – Campaign attribution parameters
• Any existing non-empty query parameters already on the request URL are preserved automatically

• Filters automatically appear based on your job data
• Location filters show hierarchical relationships (City → State)
• Department filters group related positions
• All filters work together for refined searching

• Job Function: job_function_2 (array field in Greenhouse)
• Employment Type: employment_type (Full-time, Part-time, Contract)
• Schedule Type: schedule_type (Remote, Hybrid, On-site)
• Job Category: job_category (Engineering, Sales, Marketing, etc.)
• Meta Location: meta_location_only (alternative to standard location)

1. Candidate arrives from a tracked source such as LinkedIn with URL parameters attached
2. Homepage search redirect preserves those parameters when sending the candidate to the listings page
3. Job links on the listings page keep the same parameters when the candidate opens an individual job
4. The embedded Greenhouse application receives the same parameters in its iframe URLs
5. If the landing URL contains gh_jid, the candidate is sent straight to the matching job detail page instead of stopping on the listings page

yoursite.com/careers/?gh_jid=1234567&gh_src=LinkedIn&source=LinkedIn&ccuid=abc123&utm_source=linkedin&utm_medium=social&utm_campaign=job-promo

• Teams running paid or organic recruiting campaigns on LinkedIn and other job platforms
• Sites that need cleaner source attribution inside Greenhouse
• Organizations using homepage search forms and embedded job applications
• Recruiting teams that want fewer drop-offs between campaign click and application start

• Data Source: Uses Greenhouse metadata fields stored in WordPress post meta
• Relationship Detection:
  • Locations: Uses gjlp_parent_location metadata to create parent → child relationships (2 levels)
  • Departments: Uses gjlp_department_parents metadata for parent → child grouping (2 levels)
• Note: For multi-level hierarchy (3+ levels), use the Office Hierarchy feature instead, which supports unlimited depth via the Greenhouse API
• Custom Field Support:
  • meta_location – Alternative location field
  • department – Primary department taxonomy
  • office – Office location taxonomy
• Frontend Implementation: JavaScript handles the hierarchical select interactions

• .irongforce-hierarchical-select-container – Main container
• .irongforce-hidden-select – Hidden actual select element
• .irongforce-custom-select – Custom dropdown container
• .irongforce-select-selected – Selected value display
• .irongforce-select-items – Dropdown items container
• .irongforce-select-parent – Parent option styling
• .irongforce-select-child – Child option styling
• .irongforce-select-hide – Hidden state class

• Parent Labels: Auto-generated (e.g., “All Engineering” for Engineering departments)
• Child Filtering: Selecting parent shows all child options
• Mixed Selection: Can filter by parent category or specific child items

• Companies with multiple office locations
• Organizations with complex department structures
• Sites where users need to filter by geographic regions