Paper notes and a hand-drawn diagram on a meeting table.
Illustrative stock photograph. Pexels. Not a product screenshot or evidence of a test.

PaperPort Folder Manager: Add a Reference Without Moving the Archive

Adding an existing folder through PaperPort's Folder Manager makes that location available in the Folders pane; it should not be confused with moving the archive to a new place. The distinction matters when several applications or users already depend on the original Windows path.

Before reorganizing anything, identify whether you want a different view inside PaperPort or a real change to the storage structure. Use a harmless test folder to understand the interface. Keep shared business folders unchanged until the owner has approved any actual move or rename.

Separate the application view from storage

The Folder Manager reference describes adding an existing folder and rearranging entries in the Folders pane. It also explains that removing or renaming a top-level entry added through that manager differs from operations on ordinary subfolders.

Write down the full source path before making a change. A short display name can hide whether an entry refers to a local disk, network share or external device. A familiar folder label does not establish where the actual files reside.

Define the intended outcome

If the goal is easier navigation, a managed reference may be sufficient. If the goal is changing where files are stored, plan the move with the storage owner and dependent applications. These should not be treated as two versions of the same cosmetic operation.

Protect shared paths

An actual folder move or rename can affect shortcuts, workflows, permissions and other users. Do not discover those dependencies by experimenting on a production archive. Use a sample and an approved change plan when the storage structure itself needs to change.

Add the existing location through the manager

Use the documented Folder Manager controls to browse to the intended source. Confirm the path before accepting it. The PaperPort folders overview explains that added locations can appear as top-level entries even when they are subfolders in the Windows structure.

ActionQuestion to answer first
Add an existing managed folderWhich exact storage path will the entry reference?
Rearrange managed entriesIs this only changing the navigation order?
Rename a manager-added entryDoes the documented operation affect the label or source?
Move or delete an ordinary subfolderWill this change real stored folders and files?
A woman working with a laptop, notebook and books in a home office.
Illustrative stock photograph of workplace activity, not a product screenshot or a test result. Photo: Pexels.

Verify the reference with one sample file

Open the new entry and identify a harmless file that already exists in the source folder. Compare its path and content through the normal file-access route. This confirms that the reference points to the intended location rather than a similarly named folder.

Do not copy the entire archive into another folder merely to make the navigation tree look tidy. That can create duplicate authoritative-looking documents and increase storage use. A new view should not silently become a second unmanaged archive.

Understand the different treatment of subfolders

The official manager documentation warns that operations on subfolders can affect the actual computer folder structure. Check which kind of entry is selected before renaming, moving or deleting it. The same-looking tree can contain operations with different consequences.

If you are unsure whether an action changes the source, cancel and test on a disposable folder. Record the before-and-after path outside PaperPort. Do not rely only on the application display to decide whether a storage operation occurred.

Keep network and external locations explicit

For a network folder, confirm the user's authorized access and the exact share. For removable storage, consider what happens when the device is not connected. An added reference does not copy the data into a permanently available local store.

If an entry becomes unavailable, investigate the source connection before deleting or recreating the archive. A missing drive and an empty folder are different situations. Give support the actual path and access context rather than only the managed label.

Review the result with the folder owner

Confirm that the files remain in their approved location and that normal dependent workflows still work. If a real move was authorized, verify the new path, access and any updated references as part of that separate change. Keep the old and new locations distinguishable during validation.

Maintain a small note of important managed references and their actual paths. Our PDF workflow guide covers broader document-handling choices. For PaperPort navigation, the practical safeguard is distinguishing a convenient folder reference from a real storage operation before changing a shared archive.

When the reference points to shared storage but new items are missing, use the network-folder diagnostic order.