When a contract or project package won't fit as an attachment, a download link can keep the email small. Before sending it to a client, decide who should open it and how long access should last. A link that works for you while signed in may behave differently for the recipient.
Decide what the recipient needs before creating the link
Start with the document and the people handling it. A client may need to read the agreement, pass it to a colleague, and return comments before a particular date. Choose an access period that allows that work. A link expiring before their next working day can create more correspondence than the attachment problem you were trying to solve.
Write a short description of what you are sending: the document name, version, file format, and any related deadline. If it replaces an earlier agreement, say so explicitly. The email gives the recipient context; the link gives them a download route. Neither one, on its own, tells them whether a saved file from last week is still the version they should use.
For example, name the revised file “Service agreement v3” and refer to that same version in the message. If the client already has v2, explain what the new email replaces. Ask them to report a different filename on the download page rather than continuing with whichever file is easiest to open. Clear version names make the exchange easier to check without treating the link as a system that controls every copy.
Keep the access model clear. A public download link can be opened without a TrekMail account and may be forwarded. An expiry or download limit narrows how the link can be used, but it is not a promise that only a named person can read a file already downloaded. If the document requires a different kind of controlled exchange, decide on that method before sending the link.
Also check who owns the uploaded file and who can manage its link later. If the customer asks for another day of access or reports the wrong document, somebody should know where to review the current settings. A useful handover names the file and the responsible person, not just the original email in which a long URL appeared.
Choose between an attachment and a download link
A link changes how the client receives the document. The message contains a route to download the file rather than the file as an ordinary attachment. Say that clearly, especially if your customer normally saves attached contracts from their email app. The client needs to know which action will retrieve the document.
The link does not increase an email attachment allowance. It avoids placing that large file inside the message, while the recipient's organization may still restrict links and downloads. Check that this delivery method suits the person doing the work before relying on it for a deadline.
If a smaller document would fit as an ordinary attachment, choose the method that matches the exchange you need. For the large contract in this example, use the download route and its actual access controls. Then test that route as the recipient rather than treating a successful upload as the end of the handover.
Prepare the file and a clear message
Give the file a name the recipient will recognize. “Service agreement v2” is more useful than “final-final-3.” If it updates a previously sent document, include the date or version number in both the filename and the email.
Upload through the available Drive mode or use large-file sending from webmail. When TrekMail offers to share through Drive, check that the prepared message contains the download link.
The large attachment guide explains the behavior. If an administrator disabled Drive for the mailbox, this sending method will be unavailable. Manually increasing a message's size does not remove that restriction.
Explain what the link contains in the email. Mention the format and size, especially if the recipient may download it on a phone using mobile data.
Choose a suitable access period
A public link can have an expiry and a download-count limit. This suits a one-off document transfer that should not remain available indefinitely.
Do not choose a very short period without agreement. The recipient might open the email after a weekend or pass it to the colleague responsible for the project. Allow enough time for the actual work and state the date until which the file is available.
Allow some room in the download limit too. Someone may save the file to a phone and then a computer. The public download guide explains link settings and revocation.
Drive's attachments-only mode has retention conditions. If the file needs to serve as a long-term archive, check whether the selected mode is suitable.
Test the same path the client will use
Open the public link without being signed in and compare the displayed document name with the email you are about to send. Download it and inspect the contents. That checks more than whether the upload finished: the file could be correct in Drive while the message contains a link to a different version.
Choose the access period and download allowance with the test and the recipient's work in mind. Someone may inspect the agreement on a phone before saving it on a computer. A very tight limit can make that ordinary workflow difficult. Check the actual controls and behavior in your account rather than promising an unlimited number of downloads or permanent availability.
If the client cannot open the link, ask what they see. An expired or revoked link, a wrong filename, and a corporate download restriction call for different responses. Check the link state before sending the same URL again. If you create a replacement, explain which message and document it supersedes so the customer does not have to guess between two similar offers.
When access should end, review the link separately from the file you retain for your own records. Revoking a public link stops future access through that route; it does not remove a copy the client has saved. If the content was wrong, send a clear correction as well as changing the access. The successful outcome is a recognizable document that the intended recipient can retrieve during the agreed period, with an understandable process for later corrections.
What to do after sending
If you shared the wrong document, revoke the link and create a new one for the correct file. Tell the recipient about the change so they do not use the outdated version.
Revocation stops further access through the link. It doesn't delete a copy already downloaded to someone else's device. Correcting a document therefore means both closing the old link and explaining which version is current.
When the project ends, decide whether to keep the file in Drive. Storage is shared with other account data, so allow for the space you will need.
Review the sharing guide before using a link for a sensitive document. Choose the access controls that actually appear in your account; a share link is not an enlarged email attachment.
Related reading
- The Email Attachment Size Limit, and How to Stop Hitting It
- Send a Share Link Instead of an Attachment (and Stop Hitting the 25 MB Wall)
- Can I edit a Drive file through WebDAV like a local file?
- Can we move just email and keep our existing work apps?
- Schedule a client reply for their morning, not yours