civiform · AlvieH · Feb 10, 2026 · Feb 6, 2026 · Feb 10, 2026 · Feb 10, 2026
diff --git a/docs/.gitbook/assets/eligibility-condition-highlight-add-subcondition.png b/docs/.gitbook/assets/eligibility-condition-highlight-add-subcondition.png
diff --git a/docs/.gitbook/assets/eligibility-condition-mutliple-subconditions.png b/docs/.gitbook/assets/eligibility-condition-mutliple-subconditions.png
diff --git a/docs/.gitbook/assets/eligibility-condition-save-and-exit.png b/docs/.gitbook/assets/eligibility-condition-save-and-exit.png
diff --git a/docs/.gitbook/assets/eligibility-multiple-conditions.png b/docs/.gitbook/assets/eligibility-multiple-conditions.png
diff --git a/docs/.gitbook/assets/eligibility-no-available-questions.png b/docs/.gitbook/assets/eligibility-no-available-questions.png
diff --git a/docs/.gitbook/assets/empty-edit-eligibility-page.png b/docs/.gitbook/assets/empty-edit-eligibility-page.png
diff --git a/docs/.gitbook/assets/empty-eligibility-condition.png b/docs/.gitbook/assets/empty-eligibility-condition.png
diff --git a/docs/.gitbook/assets/filled-eligibility-condition.png b/docs/.gitbook/assets/filled-eligibility-condition.png
diff --git a/docs/.gitbook/assets/htmx-alert-failed-request.png b/docs/.gitbook/assets/htmx-alert-failed-request.png
diff --git a/docs/.gitbook/assets/predicate-edit-add-new-conditions.png b/docs/.gitbook/assets/predicate-edit-add-new-conditions.png
diff --git a/docs/.gitbook/assets/program-view-edit-eligibility-condition.png b/docs/.gitbook/assets/program-view-edit-eligibility-condition.png
diff --git a/docs/.gitbook/assets/program-view-eligibility-condition-display.png b/docs/.gitbook/assets/program-view-eligibility-condition-display.png
diff --git a/docs/.gitbook/assets/screen-with-visibility-condition.png b/docs/.gitbook/assets/screen-with-visibility-condition.png
diff --git a/docs/.gitbook/assets/visibility-no-available-questions.png b/docs/.gitbook/assets/visibility-no-available-questions.png
diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md
@@ -17,7 +17,8 @@
     * [Create a program](user-manual/civiform-admin-guide/create-a-program.md)
     * [Edit a program](user-manual/civiform-admin-guide/edit-a-program.md)
     * [Show or hide questions based on inputs](user-manual/civiform-admin-guide/show-or-hide-questions-based-on-inputs.md)
-    * [Manage program eligibility](user-manual/civiform-admin-guide/manage-eligibility.md)
+    * [Manage program eligibility and visibility](user-manual/civiform-admin-guide/manage-predicates.md)
+    * [Manage program eligibility (legacy)](user-manual/civiform-admin-guide/manage-eligibility.md)
     * [Manage address & service area validation](user-manual/civiform-admin-guide/manage-address-correction-and-service-area-validation.md)
     * [Manage notifications](user-manual/civiform-admin-guide/manage-notifications.md)
     * [How to publish programs](user-manual/civiform-admin-guide/publish-a-program.md)

diff --git a/docs/user-manual/civiform-admin-guide/manage-eligibility.md b/docs/user-manual/civiform-admin-guide/manage-eligibility.md
@@ -1,4 +1,6 @@
-# Manage program eligibility
+# Manage program eligibility (legacy)
+
+*Note: Documentation for the revamped version of program eligibility and visibility is available at [Manage program eligibility and visibility](manage-predicates.md)*
 
 There are programs that may have strict criteria for eligibility. For example, if an Applicant’s date of birth is earlier than the qualifying year, they are ineligible for the program.
 

diff --git a/docs/user-manual/civiform-admin-guide/manage-predicates.md b/docs/user-manual/civiform-admin-guide/manage-predicates.md
@@ -0,0 +1,105 @@
+# Manage program eligibility and visibility
+
+*Note: Unless otherwise noted, assume that directions apply to both eligibility and visibility logic.*
+
+## Eligibility
+
+There are programs that may have strict criteria for eligibility. For example, if an Applicant’s date of birth is earlier than the qualifying year, they are ineligible for the program.
+
+Using eligibility conditions, CiviForm Admins can screen applicants who don't meet the minimum requirements for a program early in the application process, as well as show applicants cases when there is a program they may qualify for, based on their previous answers.
+
+## Visibility
+
+CiviForm Admins may wish to hide or show certain screens in certain cases to better control program flow. For example, if an Applicant stated they have no dependents in their most recent taxes, they can skip the screen in which applicants provide information on dependents.
+
+Using visibility conditions, CiviForm Admins can show or hide certain program screens for applicants, based on their answers to questions on previous screens.
+
+## Adding new conditions
+
+When viewing a screen in the program edit view, access to eligibility and visibility conditions are available at the "Add eligibility conditions" / "Add visibility conditions" buttons:
+
+![Program blocks view with Add visibility conditions and Add eligibility condition buttons highlighted](../../.gitbook/assets/predicate-edit-add-new-conditions.png)
+
+Clicking one of those will bring you to the edit view. You can add a new condition using the "Add Condition" button.
+
+![Edit eligibility condition view with "Add Condition" button highlighted.](../../.gitbook/assets/empty-edit-eligibility-page.png)
+
+### A note on available questions
+
+There may be no available questions to use within conditions. Invalid question types include: 
+
+* File questions
+* Enumerator questions. 
+
+If there are no available questions to use, you may see an alert like the following:
+
+![Alert that states "There are no available questions on this screen with which to set an eligibility condition."](../../.gitbook/assets/eligibility-no-available-questions.png)
+
+**Visibility conditions** take their questions from all previous program screens, so the alert will show as the following:
+
+![Alert that states "There are no available questions on preceding screens with which to set a visibility condition for this screen."](../../.gitbook/assets/visibility-no-available-questions.png)
+
+## Editing conditions
+
+On adding a condition, you will be greeted with an empty condition block:
+
+![An eligibility condition with nothing selected and blank/disabled dropdowns.](../../.gitbook/assets/empty-eligibility-condition.png)
+
+On selecting a question, you will be able to enter values and control the logical conditions. 
+
+Admins can configure:
+* **Question:** The question controlling the logic for this subcondition.
+* **Field:** For question types with multiple pieces of data (e.g. "First Name", "Last Name"), which field is used for this subcondition.
+* **State:** The logical operator for this subcondition (e.g. "Greater than", "Less than", "Equal to")
+* **Value:** The value compared to the applicant's answer to this question, for eligibility and visibility decisions.
+
+***Example:** The following applicant will be eligible if they are between the ages of 18 and 35.*
+
+![An eligibility condition with date question selected and values of "age" between 18 and 35.](../../.gitbook/assets/filled-eligibility-condition.png)
+
+### Adding subconditions
+
+You can add multiple *subconditions* within a condition using the "Add subcondition" button:
+
+![An eligibility condition with the "Add subcondition" button highlighted](../../.gitbook/assets/eligibility-condition-highlight-add-subcondition.png)
+
+***Example:** The following applicant will be eligible if they are between the ages of 18 and 35 **AND** they think a scoop of ice cream should cost $1.*
+
+![An eligibility condition with multiple subconditions. Subcondition 1 is true if the applicant is between the ages of 18 and 35. Subcondition 2 is true if the applicant thinks a scoop of ice cream should cost 1 dollar.](../../.gitbook/assets/eligibility-condition-mutliple-subconditions.png)
+
+### Multiple conditions
+
+Multiple conditions can be composed together for more complex logic.
+
+***Example:** The following applicant will be eligible if (They are between the ages of 18 and 35 **AND** they think a scoop of ice cream should cost $1) **OR** They own a toaster.*
+
+![An eligibility condition with multiple subconditions. Subcondition 1 is true if the applicant is between the ages of 18 and 35. Subcondition 2 is true if the applicant thinks a scoop of ice cream should cost 1 dollar.](../../.gitbook/assets/eligibility-multiple-conditions.png)
+
+## Saving conditions
+
+Clicking the "Save and Exit" button at the bottom of the edit page brings you back to the program view.
+
+![An eligibility condition with the "Save and Exit" button highlighted.](../../.gitbook/assets/eligibility-condition-save-and-exit.png)
+
+The program view will now display the conditions that you set:
+
+![The program view, showing "Applicant is eligible if any conditions are true: (1) Sample Currency Question" currency is not equal to $1.00 AND "Sample Date Question" date age is between 18 and 35 (2) Sample checkbox question contains any of toaster"](../../.gitbook/assets/program-view-eligibility-condition-display.png)
+
+Clicking the "Edit eligibility conditions" button will return you to the edit view.
+
+![The program view, showing "Applicant is eligible if sample date question date age is older than 18" with the "Edit eligibility condition" button highlighted.](../../.gitbook/assets/program-view-edit-eligibility-condition.png)
+
+If a screen has *visibility conditions*, the program view will show an icon next to the screen title:
+
+![The program view, showing a screen title with an icon, denoting that the screen has visibility conditions.](../../.gitbook/assets/screen-with-visibility-condition.png)
+
+## Troubleshooting
+
+### Unable to add new conditions
+
+**Problem:** In the rare case of a CiviForm internal error, you may see the following alert:
+
+![Alert saying "We are experiencing a system error that is preventing further conditions from being added."](../../.gitbook/assets/htmx-alert-failed-request.png)
+
+**Possible causes and solutions:**
+- **Endpoint failures:** This could be due to a transient issue. Save, wait for a few (3-5) minutes and retry. If issues persist, check your endpoint logs for any errors during CiviForm's attempts to add new conditions.