Share Files with NordLocker: Choose Links, Roles and a Clear Handoff

Sharing a file privately means deciding who needs access, what they should be able to do, and when the handoff is finished. NordLocker provides more than one route, and choosing the right one matters as much as generating a link. This guide focuses on current Web Access sharing and a practical recipient check, rather than assuming every app or older tutorial provides the same controls.

NordLocker's documentation checked on October 20, 2026 describes secure links in Web Access and account-based invitations with Viewer and Editor roles. It also describes migration changes affecting older shares. The examples below are fictional workflow decisions, not a claim that the author tested a client delivery. Begin with harmless material so that recipient access can be checked before sensitive files are involved.

Define the handoff before selecting files

Write down the recipient, the exact material, and the intended action. A client who needs to read a final PDF has a different requirement from a colleague who must organize project files. Decide whether the recipient needs ongoing access or a one-time delivery. This prevents accidentally sharing an entire working folder when a single final document would satisfy the request.

For a fictional design consultant, the handoff might be one approved proposal and two reference images. Draft estimates and notes belong outside that selection. Review the contents and filenames before starting. Encryption does not correct an accidental overshare: if you deliberately grant access to the wrong material, the intended security mechanism can still deliver the wrong material perfectly.

Choose between a link and an account invitation

A secure link is useful when you want a recipient-oriented delivery route with explicit link settings. Account invitations are useful when you want to associate access with a named NordLocker user and select a role. Check the recipient requirements in current support before choosing. Do not assume the same experience for someone who already uses the service and someone receiving a file for the first time.

Ask whether a download is acceptable. If the recipient is allowed to download the file, recognize that a saved copy has a separate lifecycle after delivery. Removing access later cannot be assumed to erase copies the recipient already obtained. If your requirement is stricter than normal file delivery, clarify it before using any sharing tool rather than expecting revocation to act as remote deletion.

Generate a link in Web Access

NordLocker's current link-sharing guide describes selecting the file or folder, opening Copy link, and choosing Generate link. The settings include an expiration date and a security-code option. Keep the code enabled for the protected handoff described here, and choose an expiry consistent with the actual deadline. Avoid retaining indefinite access simply because you have not decided when the project ends.

Copy the intended link and code carefully. NordLocker recommends sharing them separately. Confirm the recipient's contact details through a known channel, and use an appropriate second route for the code. Do not paste confidential access material into a public project thread. A private link is still something to handle deliberately; a recipient's identity and communication channel remain part of the process.

Explain the delivery clearly

Send a short message describing what the recipient will find, why you are sending it, when access expires, and how the code will arrive. For example, an approved message could explain that the folder contains a proposal and two reference images, with access available for the review period. Keep the message consistent with the actual shared contents and avoid including unneeded personal or account information.

The code should not be confused with your Cloud password or account password. Never send either of those secrets as a sharing shortcut. If the recipient reports difficulty, inspect the link settings and documented recipient route instead. A clear handoff reduces the chance that someone will ask for broader access because they cannot tell which file, account, or code the delivery expects.

Use an account invitation for a role-based workflow

The current Web Access email-sharing guide describes selecting Manage Access, choosing Add people, entering the recipient's email, selecting a role, and inviting them. It identifies Viewer and Editor as distinct permissions. Assign the least access needed for the job. Someone reviewing a final document should not receive edit capability merely because the project folder contains working material elsewhere.

Explain what acceptance looks like and confirm the intended account with the recipient. The current support guide describes accepting shared items through the Shared area. A sent invitation is not proof that the right person accepted it or can access the intended contents. Test the workflow with a non-sensitive item if the recipient has never used it, and avoid promising that this replaces every collaborative editing feature they may expect.

Verify the recipient view with harmless content

Before a significant delivery, use a disposable sample with the same route and settings. Ask the intended recipient to confirm the file name, visible contents, and expected action. A simple acknowledgment such as “I received the email” is not the same as confirming that the correct item opened. For role-based access, verify that the role matches the task without asking the recipient to alter valuable documents as a test.

Keep verification proportionate. A single PDF handoff may only need confirmation that the named final document opens. A structured folder transfer may need a file list and content checks. Record any failure and fix its cause before repeating the delivery with sensitive material. Sending more copies through alternative channels can create confusion about which version and access route are authoritative.

Close link access when the task is finished

NordLocker's Web Access guide documents returning to the item's link controls and choosing Delete link, then confirming. Use that control when the delivery no longer needs to remain available, and check that your intended link is the one affected. Deleting a link is an access change; it is different from deleting the underlying file or recalling downloads someone already saved.

For an account invitation, review the current access-management controls and remove access as appropriate to the relationship. Keep a short record of what was shared and why. This is especially useful when a project spans months or includes several recipients. Do not treat a folder's familiar name as proof its membership still matches the people currently working on the project.

Check migration and application differences

NordLocker's New Generation upgrade guidance says existing shares and links can be reset during migration. A returning user should therefore recheck old deliveries and regenerate or re-share through the current workflow when required. Do not promise that a previously sent link remains valid merely because the underlying file still appears in the account. Access state and stored content are separate things.

Current support also identifies platform differences, including Windows email-sharing availability and Web Access-specific link generation. Follow the documented web route for this tutorial instead of assuming all mobile or desktop versions expose identical actions. A control described as coming soon is not a capability you can rely on for today's deadline. If a required workflow is missing, choose an available supported route or another approved delivery method.

Keep privacy claims proportionate

Encrypted delivery helps protect content within the service's documented model, but it does not validate the business identity of a recipient or secure every device they use. Confirm addresses, keep accounts protected, and share only material the recipient is entitled to receive. An unexpected request for a new delivery destination should be verified independently before access changes, even when it appears in an existing conversation.

Your next step is to complete one harmless recipient test with the intended link or role, including closing access afterward. That small exercise establishes whether the workflow fits both sides. Once it does, you can deliver the actual files with clearer expectations about contents, permissions, expiry, and the limits of revoking access after a copy has left the service.