Skip to main content

People XD Integration

Set up your People XD Recruitment integration to publish vacancies and manage applications through your career site.

Written by Grace
Updated over 2 months ago

Overview

This article helps you configure the integration between People XD Recruitment and your careers website. People XD acts as the single source of truth for vacancy information, publishing jobs automatically to your careers site where applications flow back into PeopleXD for management.

You'll learn how to set up permissions, configure vacancy publishing, manage application forms, and handle candidate


Key benefits

  • Publish vacancies from PeopleXD directly to your careers website without manual updates.

  • Manage internal and external candidates in a single system with unified workflows.

  • Capture application data automatically through customised website's forms.

  • Control which users can publish, authorise, and manage vacancies based on department access.

  • Screen candidates automatically using killer questions configured in your application forms.

  • Handle candidate anonymisation and CV parsing for fair hiring processes.

  • Track applications through automated status updates and email notifications.

  • Streamline your recruitment workflow by bringing external and internal hiring into one system.


Before you start

Before configuring the integration, make sure you have:

  • Admin access to both PeopleXD Recruitment and your website.

  • Department structure configured in PeopleXD to control vacancy visibility and user access.

  • Security profiles set up for recruitment administrators, managers, and hiring teams.

  • Clear understanding of which team members need to publish vacancies and manage applications.

πŸ“Œ Note: This article focuses on integration configuration rather than detailed People XD security setup or website design.


Understanding the integration workflow

The PeopleXD and your website's integration follows a structured recruitment flow with clear data direction.

Job data flow:

  • Jobs are created and managed exclusively in People XD.

  • Vacancies publish automatically to your careers website.

  • PeopleXD acts as the single source of truth for vacancy information.

  • Access Volcanic serves as the publishing and application capture layer.

Application data flow:

  • External candidates apply using your website's application forms.

  • Applications appear automatically in People XD for recruiters to manage.

  • Internal candidates continue to see vacancies through People XD portals.

  • External candidates access vacancies on your careers website.

After hiring:

Once hired, successful candidates move from recruitment to the People Management system for ongoing HR administration.

πŸ“Œ Note: Job disciplines are managed your career website and pulled into PeopleXD to prevent duplication issues. Set up disciplines in your website before they become available in PeopleXD.


Publishing vacancies to your careers website

Understanding vacancy publishing permissions

Publishing to your careers website requires specific menu options and web services.

Users need access to:

  • The Vacancy Status screen.

  • Your website's publishing web services.

Without both, the Publish, Unpublish, and Relist buttons won't appear when managing vacancies.

Required web services for publishing

Enable these web services for users who publish vacancies. The word "volcanic" in these service names refers to your website's platform integration.

  • Get vacancy volcanic retrieves vacancy status and overview from the careers website integration.

  • Update vacancy volcanic saves vacancy status and overview changes to the integration.

  • Update vacancy volcanic publish publishes vacancies to your Access Volcanic careers website.

  • Update vacancy volcanic unpublish expires or unpublishes vacancies from your careers website.

  • Update vacancy volcanic relist relists expired vacancies on your careers website.

Assign the Recruitment Vacancy Status menu option in the CorePortal to provide screen access.

Authorising vacancies before publishing

Vacancies must be authorised before they can be published to your careers website.

  1. Create and configure your vacancy in PeopleXD.

  2. Navigate to Authorise Vacancy.

  3. Review the vacancy details.

  4. Approve the vacancy for publishing.

πŸ“Œ Note: Users need the Authorise Vacancy menu option in the CorePortal (under eRecruitment) this step.Configuring the Reports To field

The Reports To field shows candidates who they will report to if successful.

To configure this correctly, follow these steps:

  1. Navigate to CoreHR Back Office.

  2. Click CorePersonnel, then Recruitment, then Reference, then Recruitment Parameters.

  3. Verify your Reporting to Org Group and Reporting to Role settings.

  4. Open People Management, then Data Centre, then Maintain Organisation Roles.

  5. Assign the correct reporting manager to your organisation roles.

Publishing a vacancy to your careers website

Once authorised, you can publish your vacancy.

  1. Open the Recruitment Dashboard.

  2. Navigate to the Vacancies tab.

  3. Select your vacancy and open Vacancy Status.

  4. Check that Job Posting details are complete including advertise channel and dates.

  5. Click Publish to make the vacancy live on your careers website.

The vacancy appears on your website according to the opening and closing dates you've set.

πŸ“Œ Note: Featured vacancies appear at the top of job searches on your careers website.

Updating live vacancies

Changes to published vacancies need to be pushed to your careers website.

  1. Make your changes in the relevant vacancy tab such as Job Advert or Job Description.

  2. Click Update Live Job to push changes to all live channels including your website.

Managing vacancy expiry dates

PeopleXD calculates expiry dates automatically from your closing dates.

How expiry dates work:

  • The system uses the latest closing date across all job posting channels as the expiry date.

  • If you set an expiry time, applications close at that time.

  • Without an expiry time, candidates can apply until the end of the expiry date.

Default expiry behaviour:

If no expiry date is provided when publishing from PeopleXD, Access Volcanic automatically applies a default 30-day expiry from the publication date to prevent jobs remaining open indefinitely.

πŸ€“ Tip: Always set closing dates in PeopleXD before publishing to control expiry dates precisely and avoid relying on default behaviour.


Managing vacancy content and structure

Job descriptions and formatting

Job descriptions support rich formatting including headings, bullet points, and numbered lists.

Key features:

  • Your formatting appears on your careers website exactly as you create it in PeopleXD.

  • The job description field supports extensive content without restrictive character limits.

  • You can include detailed role descriptions, responsibilities, requirements, and other relevant information.

Adding vacancy documents

Upload documents to provide additional information to candidates.

  1. Open your vacancy and navigate to Vacancy Documents.

  2. Click Add to upload a document up to 10MB.

  3. Choose where the document appears such as Job Specification, Application Form, or Online Interview Panel.

  4. Save your changes.

Documents marked as Job Specification appear before candidates start their application. Application Form documents appear during the application process.

Creating question categories

Question categories are reusable question sets you can add to multiple vacancies.

  1. Open the Recruitment Dashboard.

  2. Click Toolbox, then Vacancy Question Categories.

  3. Click Add to create a new category.

  4. Enter a reference code up to 13 characters and description up to 40 characters.

  5. Set the Active flag and save.

πŸ€“ Tip: Use question categories for standard question sets like right-to-work checks or business-unit-specific profiles.

⚠️ Important: Creating additional application questions in your career website is strongly discouraged when using the PeopleXD integration.

Questions created on your website will not map back to People XD. This only works if matching reference data already exists in PeopleXD. This causes common data issues where:

  • Application responses don't appear in PeopleXD reports.

  • Question data cannot be used for screening or analysis.

  • You cannot track or report on responses within PeopleXD.

Standard fields like phone number, address, country, and postcode transfer reliably because they use predefined mappings. However, custom questions created in your career website typically fail to sync properly.

Recommendation: Create all application questions within People XD itself. This ensures reliable data capture, proper reporting, and full integration between systems.

Adding questions to categories

Build your question sets by adding individual questions.

  1. In Vacancy Question Categories, click View Questions for your category.

  2. Click Add to create a new question.

  3. Choose an answer type such as drop-down, free text, numeric, or radio button.

  4. Set the sequence, active status, and whether the question is mandatory or private.

  5. Save your question.

πŸ“Œ Note: Questions marked as Private are hidden from managers and interview panel members but visible to recruitment administrators.

Configuring killer questions

Killer questions automatically screen out unsuitable candidates based on their answers.

Step 1: Configure the unsuitable status

  1. Open Administrator Dashboard.

  2. Click Site Manager, then Admin Settings.

  3. Search for erq_unsuitable_status.

  4. Set the value to your unsuitable applicant status code (typically a code like UNS meaning unsuitable).

Step 2: Mark unsuitable answers

In your question setup, enable Unsuitable Answer for any answer option that should disqualify candidates.

When candidates select an unsuitable answer and submit their application, their status changes automatically to the unsuitable status you configured.

⚠️ Important: Killer questions only work with select or radio button answer types.

πŸ“Œ Note: Your website vs PeopleXD killer questions: Your career website has its own killer questions feature that works differently:

  • Your site's killer questions prevent candidates from submitting applications immediately when they select an unsuitable answer.

  • PeopleXD killer questions allow applications to be submitted but automatically change the applicant's status to unsuitable after submission.

You'll need to choose which approach works best for your recruitment process.

Adding ad-hoc questions to single vacancies

Questions added directly to a vacancy only appear for that specific role.

  1. Open your vacancy and navigate to Current Questions.

  2. Click Add Question.

  3. Configure your question including type, mandatory setting, and privacy.

  4. Save the question.

These questions work the same way as category questions but aren't reusable across other vacancies.


Managing applications from your careers website

Viewing submitted applications

Applications from your careers website appear in the Applicants widget.

  1. Open the Recruitment Dashboard.

  2. Click the Applicants tab.

  3. Select an applicant to view their details.

  4. On Competition Details, click View to see their complete application form.

The application form shows all responses from your Access Volcanic careers website including any vacancy-specific questions.

πŸ“Œ Note: Recruitment administrators see all application details, but managers and interview panel members cannot see diversity questions or questions marked as private.

πŸ“Œ Note: Learn more about setting up user access and permissions for applications in the People XD Help Centre.

Using Applicant One View

Applicant One View provides a central location for reviewing all candidate information.

What it includes:

  • Questions from both PeopleXD and your website's application forms.

  • Diversity data.

  • All attachments including files uploaded by applicants and merged process documents.

  • Application responses, assessment scores, and activity history.

This unified view gives recruitment administrators access to everything about a candidate in a single screen.


Configuring Volcanic mapping for custom fields

Understanding custom field mapping

Some organisations use Volcanic mapping to control which PeopleXD fields are sent to Access Volcanic as custom fields.

How it works:

  • The integration typically supports up to five custom fields.

  • These can be mapped from PeopleXD hierarchy fields and a Recruitment Custom field.

  • This lets you automatically choose which Access Volcanic application form to use based on PeopleXD field values.

πŸ“Œ Note: Standard job fields use fixed, predefined mappings that cannot be customised.

Setting up custom categories

If using job advert custom categories, set up your reference data first.

  1. Open People Management.

  2. Navigate to Reference Data, then Recruitment Custom Data.

  3. Create your custom categories.

  4. Ensure matching custom categories exist in your Access Volcanic website.

Your website's application forms can then use these custom fields through usage conditions to display different forms based on vacancy attributes.

⚠️ Important: Your website's custom categories have limited flexibility in PeopleXD integrations:

  • Custom Category 1 maps to Company.

  • Custom Category 2 maps to Management Unit.

  • Custom Category 3 maps to Department.

You cannot repurpose these mappings for other uses such as job type or work arrangement. Consider alternative approaches rather than relying on custom categories for PeopleXD integrations.


Managing candidate anonymisation and CV parsing

Understanding candidate anonymisation

Candidate anonymisation helps reduce unconscious bias by hiding personal information when candidates are at specific applicant statuses in your recruitment process.

⚠️ Important: Anonymisation is a complex feature with significant limitations:

  • It does not fully anonymise all candidate data at every stage.

  • You must read the complete configuration guide before implementation.

  • Understanding what data remains visible and where anonymisation applies is essential.

How anonymisation works

Anonymisation is status-specific. You choose which recruitment stages use anonymisation, such as shortlisting or initial interview stages.

When a candidate is at an anonymised status, the following information is hidden in Applicant One View:

  • Photo, name, and title.

  • Contact details including phone numbers, email address, and postal address.

  • CV document (replaced with an anonymised version).

You can also configure optional redaction for:

  • Employment history organisation names and dates.

  • Education body names and dates.

What anonymisation does NOT hide

Several data types remain visible even when anonymisation is enabled:

  • Cover letters and attachments: Any documents other than the CV are not anonymised.

  • Application answers: Responses to application questions are fully visible.

  • Candidate summaries: Profile summaries generated by CV parsing are not anonymised.

  • Email previews: Correspondence history may display personal information.

  • Applicant Details and Application Details screens: These screens show full candidate data regardless of anonymisation status.

⚠️ Important: Because cover letters, application answers, and other content are not anonymised, users may still identify candidates from this information. Effective anonymisation requires limiting which screens users can access and controlling who can move candidates between statuses.

Where to find full implementation guidance

Anonymisation requires careful planning, user access controls, and ongoing monitoring. The complete Candidate Anonymisation & CV Parsing guide covers:

  • Detailed configuration steps for all anonymisation parameters.

  • Complete data visibility matrices showing what is hidden on each screen.

  • Admin override permissions for accessing anonymised data.

  • CV parsing configuration and supported file types.

  • Best practices for rolling out Applicant One View.

  • Monitoring shortlisting bias using Applicant Status History reports.

  • Controlling status changes in the Interview Panel widget.

πŸ“Œ Note: Access the full guide from the PeopleXD Recruitment user guides page, or download the Candidate Anonymisation & CV Parsing PDF directly.

Contact your PeopleXD Account Manager or Customer Success Manager for implementation support.

Quick start: Enabling anonymisation for a status

This quick start shows the basic steps only. You must read the full guide before implementing anonymisation.

  1. Open the Recruitment Dashboard, then click Toolbox.

  2. In the My Recruit Toolbox widget, click Open on Applicant Status.

  3. Click the three-dot menu on the relevant status, then click Status Details.

  4. Turn the Anonymise Candidate Data toggle on.

  5. Click OK.

  6. Repeat for each status you want to anonymise, then click Save.

Quick start: Enabling CV parsing

CV parsing automatically reads uploaded CVs and extracts structured information including candidate summaries, employment history, education history, and skills.

  1. Open the Administrator Dashboard.

  2. Click Site Manager, then Admin Settings.

  3. Search for enable_cv_parsing.

  4. Click Edit, set the value to Y, then click OK.

Parsed CV information appears in Applicant One View on the CV Profile tab.

πŸ“Œ Note: CV parsing is only available with XD Recruitment Premium and requires your new careers website. The parsing process is point in time, meaning only CVs added after enabling will be parsed. Cover letters are not parsed.

Understanding parsed CV data

The CV Profile tab displays:

  • Candidate Summary: Profile text extracted from the CV.

  • Generated Summary: Automated summary if no profile text is available (requires additional configuration).

  • Employment History: Job titles, organisation names, dates, and role descriptions.

  • Education History: Qualifications, institutions, and dates.

  • Skills: Skills supplied on the CV or inferred by the parsing process.

⚠️ Important: Skill names may not exactly match the wording on the CV. Skills are normalised using a skills taxonomy. You cannot currently search or filter by parsed skills.

CV parsing configuration and permissions

The full guide explains:

  • How to configure the Generated Summary output.

  • How to control what employment and education data is hidden when candidates are anonymised.

  • Required web services permissions for viewing parsed data.

  • Supported CV file types (including Word, PDF, Excel, images, and many others).

  • Accuracy considerations and known limitations.

πŸ“Œ Note: Refer to the complete guide for full configuration details.

Setting up status-driven emails

Configuring sender details

Set up the from name and email address for recruitment emails.

  1. Open Administrator Dashboard, then Site Manager, then Admin Settings.

  2. Search for cp_recruit_email_fromn and set your sender name.

  3. Search for cp_recruit_email_frome and set your sender email address.

  4. Save your changes.

Creating email templates

Email templates generate automatically when applicant status changes.

  1. Open Recruitment Dashboard, then Toolbox, then Applicant Status

  2. Select your status and click Email Template.

  3. Choose a data source such as Application Detail.

  4. Configure your subject and body using merge fields. Merge fields are placeholders shown as <<field>> that automatically populate with candidate or vacancy data when emails are sent.

  5. Save your template.

  6. Back on Status Detail, enable Email Template after status change.

  7. Save your status configuration.

πŸ“Œ Note: Emails are created per applicant and don't automatically trigger from all screens that change status.


Best practices

  • Always make job updates in PeopleXD rather than directly in your website to prevent changes being overwritten.

  • Set up department access before granting users recruitment permissions to prevent unauthorised vacancy access.

  • Configure job disciplines in your website first before they become available in PeopleXD.

  • Set closing dates in PeopleXD before publishing to control expiry dates precisely and avoid default 30-day expiry behaviour.

  • Create critical screening questions needed for reporting directly in PeopleXD rather than your website to ensure reliable data capture.

  • Test the full workflow from vacancy creation to application submission before going live.

  • Use question categories for standard question sets rather than recreating questions for each vacancy.

  • Configure killer questions carefully to avoid accidentally screening out qualified candidates.

  • Review email templates before enabling automated status emails to ensure professional messaging.

  • Avoid repurposing custom categories for uses other than their fixed mappings to Company, Management Unit, and Department.

  • Train recruitment administrators on both PeopleXD and your website to support end-to-end processes.

  • Contact your Customer Success Manager rather than attempting to self-configure the integration as it requires internal team involvement.

πŸ“Œ Note: The People XD' recruitment Help Centre contains additional recruitment configuration guidance. Also see People XD's Recruitment user guides covering all aspects of PeopleXD recruitment functionality.


FAQs

Q1: Why can't I see the Publish button on Vacancy Status?

  • Answer: The Publish button doesn't appear when you're missing required permissions. You need both the Vacancy Status menu option and the website's publishing web services enabled in your security profile. Check with your PeopleXD administrator to assign these permissions to your user account.

Q2: How do I know which application form will be used for a vacancy?

  • Answer: Your website uses usage conditions and custom field values to determine which application form displays. Review your website's mapping configuration or contact your Customer Success Manager for details about your setup.

Q3: Are diversity questions visible to managers in application forms?

  • Answer: Managers and interview panel members cannot see diversity questions in application forms. Questions marked as private are also hidden from managers and panel members. Only recruitment administrators can view all application responses including diversity questions and private questions.

Q4: What happens if I unpublish a vacancy that's already live?

  • Answer: The vacancy is removed from your careers website immediately. PeopleXD recalculates the expiry date from any remaining job posting channels.

Q5: Do already-published vacancies need re-authorisation when updating them?

  • Answer: You don't need to re-authorise changes to vacancies that are already published. Once a vacancy is live, you can make updates and use the Update Live Job button to push changes to your careers website without going through additional authorisation steps.

Q6: How do killer questions screen out candidates?

  • Answer: When a candidate selects an answer marked as unsuitable and submits their application, their status changes automatically to the unsuitable status configured in Admin Settings.

  • This is how PeopleXD killer questions work within the integration. Your career website also has its own killer questions feature that works differently by blocking candidates before submission rather than allowing them to complete their application.

Q7: What's the difference between my website's killer questions and PeopleXD killer questions?

  • Answer: Your career website's killer questions stop candidates immediately when they select an unsuitable answer, informing them they're not eligible and preventing application submission so unsuitable applications never reach PeopleXD.

  • PeopleXD killer questions allow candidates to complete and submit their application normally, then automatically change the applicant's status to unsuitable after submission, meaning all applications reach PeopleXD including unsuitable ones that need management or review.

  • If using your career website's killer questions, the PeopleXD killer question functionality won't apply because ineligible candidates are blocked before submission, so consider whether your process benefits more from preventing unsuitable applications entirely or from receiving all applications but having unsuitable ones automatically flagged for potential review.

Q8: Can question categories be reused across multiple vacancies?

  • Answer: Question categories can be used across multiple vacancies. They're designed to be reusable, which ensures consistency in your screening questions and saves time when creating new roles. Once you create a question category, you can add it to as many vacancies as needed.

Q9: Why is my Reports To field empty on new vacancies?

  • Answer: The Reports To field derives from your organisation role configuration in PeopleXD. Check your Recruitment Parameters and Maintain Organisation Roles settings to ensure reporting managers are correctly assigned.

Q10: What's the difference between Job Specification and Application Form documents?

  • Answer: Job Specification documents appear before candidates start their application, while Application Form documents appear during the application process. Online Interview Panel documents are only visible to interviewers.

Q11: Can I edit a vacancy after publishing it to my careers website?

  • Answer: You can edit vacancies after publishing them to your careers website. Make your changes in the relevant PeopleXD screens, then click Update Live Job to push the updated information to your careers website. The changes appear on your website immediately.

Q12: How do I extend a vacancy that's about to expire?

  • Answer: Update the closing date in Vacancy Status, then click Update Live Job to push the new expiry date to your careers website. Alternatively, use the Relist button after a vacancy has expired.

Q13: What happens to applications if I delete a vacancy?

  • Answer: Existing applications remain in PeopleXD and can still be processed. However, new candidates cannot apply once the vacancy is removed from your careers website.

Q14: Can I edit job details directly on my website?

  • Answer: Do not edit job details directly in your career website when using the PeopleXD integration. PeopleXD is the single source of truth for all vacancy information, and any manual changes made in your career website will be overwritten the next time the job is updated in PeopleXD.

Q15: What happens if I don't set an expiry date in PeopleXD?

  • Answer: If no expiry date is received from PeopleXD, your career website automatically applies a default 30-day expiry to the vacancy. To control expiry dates precisely, always set closing dates in PeopleXD before publishing.

Q16: Can I set up the PeopleXD integration myself?

  • Answer: The integration cannot be fully set up by customers alone. Setup requires involvement from both your career website's internal teams and PeopleXD internal teams to configure API keys, webhook endpoints, and permissions correctly. Contact your Customer Success Manager to initiate integration setup.

Q17: Is it possible to customise field mappings between PeopleXD and Access Volcanic?

  • Answer: Field mapping between PeopleXD and your career website is predefined and cannot be customised. The integration uses fixed mappings for fields like job title, location, salary, and job type. You cannot remap these fields to different destinations.

Q18: Where are job disciplines managed in the integration?

  • Answer: Job disciplines are managed in your career website and then pulled into PeopleXD. This prevents duplication or mismatch issues between the two systems. Set up your disciplines in your career website first before they become available in PeopleXD.

Q19: Which system should I use to create application questions?

  • Answer: It is strongly recommended to create all application questions in PeopleXD rather than your career website. Creating questions in your career website is technically possible. However, they will not map back to PeopleXD unless matching reference data already exists. This creates common issues where application responses don't appear in PeopleXD reports.

  • The data cannot be used for screening or analysis. Standard fields like phone number, address, country, and postcode use predefined mappings and transfer reliably. Custom questions created in your career website will typically fail to sync.

  • Questions created in your career website also apply to all jobs. Questions created in PeopleXD can be job-specific. Create all application questions within PeopleXD itself to ensure reliable data capture and proper integration.

Q20: Can I use my website's custom categories with PeopleXD?

  • Answer: Custom categories have limited support in PeopleXD integrations. Your career website's custom categories map automatically to fixed PeopleXD fields: Custom Category 1 maps to Company, Custom Category 2 to Management Unit, and Custom Category 3 to Department. You cannot repurpose custom categories for other uses like job type or work arrangement. Consider custom categories largely unsuitable for PeopleXD integrations.

Q21: How can I confirm an application has successfully synced to PeopleXD?

  • Answer: There is no customer-facing confirmation mechanism to verify successful application sync. Applications are typically confirmed by checking for application notification emails or verifying the candidate appears in PeopleXD. If applications are consistently missing, contact Support to check webhook logs and verify the integration is working correctly.

Q22: What should I do if applications are missing from PeopleXD?

  • Answer: Missing applications are one of the most common integration issues. First, verify the candidate received a confirmation email from your careers website, which indicates the application was submitted successfully. Then check PeopleXD to see if the application appears. If applications are consistently missing, contact Support to review webhook logs and investigate the data flow between systems.

Q23: Why do locations appear differently in PeopleXD compared to my career website?

  • Answer: Location mismatches occur when location data is structured differently between systems. This is another common integration issue. Ensure your location reference data is configured consistently in both PeopleXD and your career website. If mismatches persist, contact Support to review how location data is being mapped in the integration.

Q24: Are there separate charges for the PeopleXD integration?

  • Answer: The People XD integration is considered part of your career website product and is not typically charged separately, unlike some third-party ATS integrations.

  • Integration setup is generally handled during onboarding or platform migration. If you're an existing customer adopting PeopleXD, speak with your Account Manager or Customer Success Manager about the integration process.

Q25: What happens if I create a custom question in my website that doesn't match a PeopleXD field?

  • Answer: Custom questions created in your career website will not map back to PeopleXD unless matching reference data already exists in PeopleXD. This means application responses won't appear in PeopleXD reports and cannot be used for screening, analysis, or reporting.

  • Questions with standard permalinks like phone, address, and country map correctly because they use predefined mappings, but custom questions without corresponding PeopleXD reference data will fail to transfer. It is strongly recommended to create all application questions within PeopleXD itself to ensure they're captured reliably and available for reporting.

  • Contact your Customer Success Manager if you need clarification on specific question types.

Q26: Can the Access Volcanic support team help with PeopleXD setup questions?

  • Answer: The your career website's support team aren't experts in PeopleXD setup or functionality. For any questions or queries about PeopleXD configuration, features, or troubleshooting, refer to the PeopleXD team directly. You can check out the PeopleXD Recruitment Help Centre and access detailed PeopleXD Recruitment user guides to learn more about the system.

Q27: Why won't my vacancy publish or why are publish actions missing?

  • Answer: Check user permissions and vacancy authorisation first. Confirm the user has Vacancy Status menu access and that your career website publish, unpublish, and relist web services are enabled. Ensure the vacancy has been properly authorised before attempting to publish.

Q28: Why is application form content not visible in PeopleXD?

  • Answer: Enable the required web service and check user permissions. Confirm the Recruitment, then Get vacancy application details web service is enabled. Check the user has Applicant Status View access to see application forms.

Q29: Why can't managers see certain questions or answers?

  • Answer: Questions marked as Private are hidden from managers and panel members. Additionally, diversity questions are never visible to managers or panel members regardless of privacy settings. See Q3 for more details on question visibility permissions.

Q30: Why isn't killer question screening working?

  • Answer: Verify your configuration at both system and question level. Confirm erq_unsuitable_status is set to the correct applicant status code in Admin Settings. Check your question uses select or radio button answer type.

  • Verify the answer option is flagged as Unsuitable Answer. Remember that your career website and PeopleXD killer questions work differently, so if using Volcanic killer questions, unsuitable candidates are blocked before submitting applications and won't appear in PeopleXD.

  • It is strongly recommended to configure all application questions including killer questions within PeopleXD itself to ensure reliable integration and data capture. Contact your Customer Success Manager if you need clarification on specific question types.

Did this answer your question?