Attachments escape the workspace
Once a file is attached, the sender loses control: no expiry, no revocation and no record of who forwarded it.
Secure file sharing
Protected links with a password, an expiry date, a visitor limit and a download decision. Revoke access when the purpose ends.
Illustrative sharing panel based on the controls available in the product. File name and values are examples.
The sharing problem
Sending a file is easy. Closing access afterwards, and proving who had it, is the part most tools leave to the sender.
Once a file is attached, the sender loses control: no expiry, no revocation and no record of who forwarded it.
Public links stay active after the deal, the review or the semester ends, leaving an access path nobody monitors.
The same link goes to the client, the auditor and the whole internal team, with identical permissions for each.
Views and downloads are invisible, so a question about disclosure cannot be answered with evidence.
Sharing flow
Four decisions per link. They take seconds and answer the questions that arrive weeks later.
Upload the file or folder to the workspace. Choose whether the share is internal, external or public.
Add a password, an expiry date and a maximum number of unique visitors. Disable downloads when viewing is enough.
Send the link through your usual channel. For sensitive exchanges, send the password separately.
Close the link when the purpose ends. The file and its versions stay in the workspace; the access path does not.
Send the link and the password through different channels. A password sent in the same email protects the link less than it appears to.
What you can control
These are the controls available when a link is created. Availability of watermark and access contracts depends on the plan.
Require a password before the recipient can open the link.
Set the date after which the link stops working, independently of the file's retention.
Limit how many distinct recipients can open the link.
Allow viewing only, or permit the recipient to download the file.
Where the plan includes it, apply a watermark or require acceptance of an access contract before viewing.
Disable the link at any time. Existing recipients can no longer use it.
Who shares what
The same controls apply, but the sensible defaults differ between a client deliverable, an internal folder and a one-off transfer.
Deliver a proposal, a report or a final asset through a link that expires when the engagement does.
Give colleagues view or edit rights in a shared folder instead of sending new copies by email.
Send a large file to a recipient who does not need an account, with a password and an expiry date.
Honest limits
Security language should survive contact with a determined recipient. These are the boundaries we state openly.
Everabyte applies layered encryption — application level plus storage level — with owner-controlled decryption. The platform can decrypt files to serve previews and downloads; it is not a zero-knowledge or end-to-end encrypted sharing product.
If a recipient only needs to read a document, disable downloads and set an expiry date. If they need the file, grant the download and close the link when the task is complete.
Tell us who receives files outside your organisation and what must be proven afterwards. We will show you how the link controls map to that workflow.
Watermark, access contracts and audit logging depend on the selected plan.