Dreamweaver Live View authentication scope and expired credential handling

Dreamweaver Live View renders pages in a client-side sandbox for preview. The unresolved question is how this preview context relates to least-privilege authentication for server-side actions such as publishing or FTP, and how expired credentials are handled.

Current documentation references authentication settings under Preferences and notes that session tokens can expire without automatic re-authentication. The feature is described as not providing clear feedback when credentials are invalid, which can lead to silent failures in publishing operations. Behavior may differ between Dreamweaver CC 2025 and earlier versions, and the enforcement of least-privilege scopes within Live View versus the site management layer is not clearly defined.

Clarification is needed on the intended security boundary between Live View preview and server-side operations, and on the expected credential lifecycle.

Does Live View enforce least-privilege authentication scopes for server-side operations initiated from the preview? What user feedback is provided when a Dreamweaver session token or site credentials have expired? Is re-authentication expected to be manual and where is this documented?