CheckStatus Configuration overview
Updated at October 14th, 2026
Table of Contents
CheckStatus Configuration allows you to customize the status label that candidates see on each application when they use the multi-application CheckStatus experience.
When the Candidate CheckStatus Experience toggle is off, Paradox answers using the response that's configured in the CheckStatus topic from the Candidate Q&A instead of using the multi-application CheckStatus experience.
For more information, see Multi-application: Candidate experience.
Use cases
- Candidate-facing status messaging: Company/Account Admins can further customize their Candidate Q&A CheckStatus experience, providing the desired level of detail for candidates requesting an application update.
Configuration
This feature must be enabled for your account. See CheckStatus Configuration: Configuration and use.
Navigation
- Select the All Apps menu in the upper-left corner of the header and then the CMS app in its drop-down menu.
- From the left panel, select CheckStatus Configuration under Candidate Assistant Responses.
CheckStatus Configuration page
The CheckStatus Configuration page lists all journeys in your account, along with its CheckStatus Configuration status (published or unpublished) and last edited date.
When you select a journey, you can view a list where each row represents a single status in the journey. The list includes the following columns:
- Stage: The journey stage for the status (for example, Capture or Scheduling).
- Status: The specific status name within that stage.
- Default Content: The candidate-facing label that displays if the Custom Content field is empty.
- Custom Content (optional): The candidate-facing label that you can update to override the Default Content.
When candidates ask about their status during the multi-application CheckStatus experience, they view the Default Content on their application card unless you update the Custom Content. Custom journey statuses often default to display Processing until Custom Content is updated.
The CheckStatus Configuration page shows the last published version of a journey. Unpublished journey edits in Journeys are not reflected until you publish the journey.
Relevant documentation
Learn more about this feature at the CheckStatus Configuration category.
Permissions
Users will need access to the CheckStatus Configuration page through the CheckStatus Configuration permission in Roles and Permissions. By default, Paradox Admins, Company/Account Admins, and Franchise Owners will have full access to this permission, while all other user roles have view access. Contact your manager or a user who has full access to Roles and Permissions to adjust user permissions for this feature, as needed.
Frequently asked questions (FAQ)
Why is the CheckStatus Configuration section in the CMS if I cannot use it yet?
During account onboarding, the CheckStatus Configuration section in the CMS may display under Candidate Assistant Responses in the CMS, but the page stays disabled until your account finishes onboarding. After onboarding completes, users with the CheckStatus Configuration child permission can open the page and configure status labels. If the page remains unavailable after onboarding, contact your CS Representative for troubleshooting.