ShareFile can stay as a bridge, but the customer should feel TAVALIS as the real vault.
The visible customer path should move to TAVALIS now: intake, checkout, portal messages, and document visibility. Legacy file tooling may remain behind the scenes while the platform-native vault grows into the end state.
The end architecture is a TAVALIS-authenticated vault and portal surface. ShareFile remains acceptable only as a transition layer while that customer-facing system is finalized.
The client should upload identity and support files directly into TAVALIS, not through scattered mail attachments.
Each artifact should show whether it is prepared, conditional, accepted, or requires replacement.
Customer-visible document slots should later surface the safe projection of reviewed artifacts and issued records.
Legacy ShareFile remains acceptable as a bridge, but the customer-facing truth should converge into TAVALIS.
Primary identity artifact with later review-state and replacement handling.
Only required when review or compliance explicitly asks for it.
Summary pack that bridges intake completion into signature and order handoff.