# Configure Client Portal access and steps

The Client Portal is built from steps called Extranet Phases. Open System Management, then Extranet Phases, to find the step you need. A package places those steps in the order the client follows. The package's printed Document Templates list is separate from its portal phase order. Start by identifying the application, package, and affected step, then review the current sequence before making a change. A document edit and a navigation change may require different updates.

Open the relevant phase and review its document and signature controls. In this DMP Agreement example, Document Description names the item stored in the client's Extranet Documents. A description is required for that stored document. Signature Required and CoApp Signature Required are both Yes. The co-applicant requirement depends on the main signature requirement. Wet Signature controls drawn-signature input where supported, and Display Signature Clause controls the notice above it. Verify the approved document, notice, and required signers together before enabling a changed step.

Review the completion effects as carefully as the document. Is Complete Step can close all open Paperwork tasks and update client access for the application. Do not enable it simply because a page appears last in your draft. Check the intended final step and task behavior. On the client record, Send Package is also an action with effects: it creates or updates the portal account, resets the package to its beginning, and can send the configured welcome email. Inspect existing progress before sending or resetting a package.

Verify a changed package through the approved test procedure. Check its step order, required fields, client and co-applicant signatures, saved documents, and resulting tasks. Review access after completion as well. For terminal client phases, access depends on Company settings and eligibility; a configured grace period is conditional, and the default of zero disables it. Do not promise continuing access based only on a saved document. Record the reviewed package version and outcome so future changes can repeat the same checks.