# Understand Client Portal package composition

A package connects the staff workflow to the documents or steps a client receives. The printed version is made from document templates. The Client Portal version is made from portal phases. A single package may contain both. Keep those two paths separate when reviewing a problem: a correct printed packet does not prove that the portal sequence is correct.

Open System Management, choose Packages, and open the intended package. Check whether it is active, where it appears, and which agencies or companies can use it. Review the validation setting and the task to create. The package's behavior depends on these settings as well as the components it contains. Here we are inspecting a DMP Enrollment package.

Review the Extranet Phases and Document Templates separately. Identify the client information step, any document or authorization steps, and the completion step. A phase may refer to a shared document template or be reused by more than one package. Before changing a shared component, identify the other packages that use it. Avoid changing shared content merely to solve one package’s display problem.

Before releasing a package change, verify both output paths through your organization's test process. Check the printed documents and the client-facing sequence separately. Review required fields, generated content, signatures where applicable, completion state and the resulting task. Remember: the package controls availability and order; phases define the portal steps; templates supply document content. A correct printed packet alone cannot verify the client experience.