Configure Tasks, Files, and Resources
Set completion rules and share the resources clients need.
Configure each onboarding step around a clear client action. Instructions, completion rules, and access settings should agree so clients can finish without guessing.
Task checklists
Add a title for each task and choose whether it belongs to the client or the team. Review the Completion rule.
If the checklist includes team-owned tasks, use Client tasks only for client completion or remove the team-owned tasks from that required checklist. Clients cannot complete the team's tasks, so requiring every task would block them; publication checks flag this configuration.
File uploads
List the requested files and mark required items. Set allowed types, size limits, maximum file count, and the destination folder. Make the maximum count large enough for every required request.
Explain acceptable files in the step instructions. Review uploaded evidence in the resulting records before treating the request as fulfilled.
Resource library and Grant access
Add the intended files or links with clear labels. Check each link and the audience before publication. A Resource library presents a curated collection; Grant access makes the configured resources available as part of the journey.
For portal content, use files uploaded for the portal flow. If publication asks you to re-upload media for private portal access, replace the affected asset and try again. A public copy of a file does not become private just because its link appears inside the portal.
Forms and bookings
Choose the form for a Questionnaire and the booking page for a Scheduler. Review their fields, availability, and client-facing details in the source module. Completion follows the linked submission or booking event.
Hold a step for internal work
Choose Hold until released by workflow when your team must finish an approval or setup action before the next client step opens. Configure a Workflow with Make next Flow step available for the matching flow run.
Use Continuous delivery when the next step should open after the previous step. See Connect Workflows and client flows.