Send a document or folder over WhatsApp, SMS, or from your organization's official email, and define what the other party can view or do. The recipient opens the secure link and reviews the content, signs it, or sends a note — without needing an account inside the system.
Mstnd creates a share link tied to the document or folder, the recipient, the permissions, and the required action. The link is sent over WhatsApp, SMS, or email — and when email is chosen, it can be sent from your organization's official email — protected by an expiry and an OTP or identity verification. Every access and action is recorded in the sharing log inside the system.
A contract is sent as an attachment to an external advisor for review, so they save it on their device and forward it to a colleague. After sending, the organization can't stop access or know who opened the copy, and the notes come back in a separate file, disconnected from the original.
The organization sends a link tied to the document and sets the recipient, the duration, and permission to view, download, review, or sign — and when sending over email it can use the organization's official email as the sender address. OTP or Nafath can be added, and actions and replies are recorded in the document's context without granting the party an internal account.
Controlled external collaboration that can be tracked and stopped, instead of releasing a permanent copy beyond the organization's control.
The moment you send a file as an attachment, you can't control how long access lasts or which version the recipient is reviewing. If you resend a corrected copy, the party may open the old one. And when you request a signature or review, replies come back through different channels and are hard to link to the original context.
The problem isn't the sending channel itself; it's sending a copy separated from the system — without permission, tracking, or a defined action.
Choose the file or folder and specify the external entity or person. The recipient doesn't need to be a Mstnd user, and gets no access to the rest of the organization's files.
Send the invitation over WhatsApp, an SMS message, or email. The message appears with the organization's name, identity, text, and details you approve, instead of an anonymous link with no clear source. And when you choose email, you can use the organization's official email as the sender address so the invitation arrives from your approved domain.
Access can be view-only, review and comment, sign, upload a reply or document, or any action the share allows. The party sees only what they need to complete the request.
Protect the link with an expiry time, an OTP, or identity verification via Nafath depending on the document's sensitivity. Access can be closed once the action is completed or the duration ends.
The external share appears in the document log, with the party, the channel, the action, and the status. When the recipient signs, reviews, or replies, the status updates inside the system instead of waiting for a separate message.
The contracts department sends an agreement to a client over WhatsApp. The client receives a message with the organization's identity and a link valid for a defined period. They verify their identity, open the final version, and sign it. The result comes back to Mstnd and the copy is saved with the signature log — without sending the file between devices more than once.
No. The party opens the external link and performs only the action defined for them, without accessing the internal system or creating a full account.
Yes. You can share a document or a folder and define the scope of access and the available actions as needed.
Mstnd supports sending over WhatsApp, SMS, and email, with the organization's identity and message. When using email, it can be sent from your organization's official email.
Yes. The organization's official email can be used as the sender address, so the external party receives the share link from your approved domain and identity.
Yes. The share can be limited to a defined duration and permissions, and access can be closed when the duration ends or the action is completed.
Yes. An OTP or verification via Nafath can be used, depending on the share settings and the document's sensitivity.
Yes. Access, review, signing, and replies are tied to the sharing log and the document inside the system.
Send a controlled link instead of a copy you can't control.
