An unscanned document never enters the file.
Uploads undergo type, content and virus scan checks. A share link is bound to the selected document version. The e-signature connection is in preparation and is not yet available.
- Scan
- MandatoryA file that does not scan clean is not stored.
- Check
- Type · size · content25 MiB per file, plan quota and header checks for recognised formats.
- E-signature
- In preparationProvider connection and acceptance are pending; signature dispatch is not yet available.
- Link
- Time-limitedAn expiring, revocable link pinned to the selected version.
- Operation records
- User · timeCreation/change auditing does not verify the identity of every downloader.
Four stops from upload to sharing.
Scanning, storage and version-bound sharing are parts of the document workflow. The e-signature connection is planned scope; its step on this page does not show a working provider connection.
- 01/0610:14
An example upload request starts. This illustration does not upload a file or create a stored Pending record in the list.
- 02/0610:14
File size is checked against the 25 MiB limit and plan quota, and the extension against upload rules. Recognised formats also receive header checks.
- 03/0610:15
The mandatory scan runs during the upload. The document is not stored until the result is clean; if the scan cannot run, the upload is rejected.
- 04/0610:15
A new record is stored after validation and a clean scan. This example is not acceptance evidence for a running scanner or the identity of every downloader.
- 05/0610:18
This step is not yet available; it does not show a signature dispatch to a provider.
- 06/0610:19
A signed result is not promised before the technical contract and actual provider acceptance are complete.
The document is uploaded
- 01/04Scanned
An upload passes the check and the scan.
The per-file limit is 25 MiB and plan storage quota applies. Extension rules and headers of recognised formats are checked; this is not a complete parser for every format or a guarantee that every malicious file is detected. Mandatory scanning follows; a new file is not stored without a clean result.
- File name, extension and size are validated against upload rules.
- A document is not stored before the scan result comes back clean.
- If the scan cannot run, the upload is rejected; when the system cannot be sure it does not accept the file.
Illustrative upload stages
- Clean
A new record is stored after a clean scan and the other checks.
- Processing
The upload request is in progress; this does not mean a Pending record has already been stored in the list.
- Rejected
A new file is not accepted if validation or scanning fails.
- 02/04Clean
Document access is constrained by company scope.
Document access is restricted by company, branch and operation permissions. Manage viewing and download conditions through roles and permissions. An e-signature permission does not mean the provider connection is ready.
- Creation and change audit records are not an exhaustive access log of every preview/download.
- Deleted documents leave the lists; restoration depends on the retention window and permanent clean-up not having started.
- The whole life cycle is described on the document management page.
- 03/04In preparation
E-signature provider connection in preparation.
E-signature dispatch is not yet available. The intended setup supports company-selected providers; supported operations will be stated after the technical contract and provider acceptance are validated.
- Setup steps are not promised before a provider or connection method is selected.
- Document version history is not proof of a working e-signature connection.
E-signature - 04/04Time-limited link
Create a share link for the selected version.
The link is pinned to its creation-time version and can expire after 1–30 days; a password is optional. Anyone with the link and its password, if set, can access the content. Creating a link does not deliver an email or SMS. Uploading a new version does not change the version pinned to an existing link.
- The shared version does not grant access to other documents or records; the recipient is not separately verified as a client.
- Creating and closing the link is recorded.
Vekilaw is developed by Vekilaw. ISO/TSE certificate details have not been published. The MTY Cloud infrastructure scope depends on deployment and operating conditions; 99.9% availability is a target, not a measured result. See security and KVKK.
The link opens only the selected version.
Anyone holding the link and its password, if set, can open the selected version without seeing other records. Revocation, expiry and access conditions can prevent subsequent opens. Copies already downloaded are not recalled and every in-progress download is not immediately stopped.
- Scope
- The creation-time version; it does not follow new uploads.
- Duration
- 1–30 days; an authorised user can revoke it.
- Record
- Creating and closing are recorded.
What do firms ask about document security?
- 01/05
How long does the scan take?
The scan runs during the upload and the document is not stored before a clean result comes back. If the result is not clean, the upload is rejected and you upload the file again later.
- 02/05
What happens if the scan cannot run?
The upload is rejected. When scanning is not possible the system does not accept the file and never lets it be stored unscanned.
- 03/05
Which e-signature services does it work with?
The e-signature connection is not yet available. A ready service list or signature dispatch is not promised before company-selected providers technical contracts and acceptance conditions are validated. Contact us.
- 04/05
Can a signed document be changed?
A new file version does not overwrite the earlier content in place; history availability depends on deletion and retention conditions. This does not establish e-signature verification or acceptance of the provider connection that is still in preparation.
- 05/05
Who can open a share link?
Anyone with the link and its password, if set, can open its pinned version; the recipient is not verified as a client. Links expire after 1–30 days and can be revoked; they do not follow new versions or recall downloaded copies. Other records are not opened. See document management.