A custom condition is a one-off request you add to a portal for a specific client. Think of it as a free-form layer on top of the template you picked.
What Counts As A Custom Condition
- A doc you need that the template doesn't cover (e.g., "Copy of your purchase agreement signed").
- A question you need answered that the template doesn't ask (e.g., "Confirm your closing date").
- A clarification request based on something you saw in their initial submission.
Adding A Condition Before Send
While composing a portal send:
- After picking a template, scroll to Custom Conditions.
- Click + Add Condition.
- Enter a label (what the borrower sees) and pick a type:
- Document upload
- Text answer
- Yes / No
- Date
- Optionally add instructions below the label.
- Mark as Required if they can't skip it.
- Add more conditions as needed.
Custom conditions appear at the top of the borrower's portal so they don't miss them.
Adding A Condition After Send
If the portal is already out and you need more info, you have two options:
- Request more info - adds a condition mid-session. The borrower gets a notification. See Working A Portal Submission.
- Request changes - flag a specific submitted doc and ask them to redo it.
Reusing Conditions Across Clients
If you find yourself adding the same custom conditions repeatedly, it might be time to bake them into a template instead. See Creating And Editing Your Own Portal Templates.
Editing Or Removing A Condition After Send
You can remove a condition you added mid-flow. The borrower's portal updates in real-time, so a removed condition disappears from their view.
What To Do Next
- Send the portal: Sending A Portal.
- For scenario-specific bundles, use addon packs instead: Addon Packs.