Share from other apps
When the portal is installed as a PWA and the browser supports the system share menu, LadVen OS can receive material from another app. The /share-target page previews it and lets you send it to a chat or task comment.
How it works
Choose Share and LadVen in another app, review the title, text, link, and files, add an optional note, then choose Chats or Tasks. Select a recent conversation, employee, or task and send.
Chats receive one message with the text, link, and attachments. Tasks receive a comment with the same content and files. After a successful send, the one-time queue is cleared and the selected context opens.
The PWA share menu sends one temporary payload to /share-target. If the route is opened with title, text, and url query parameters, the page accepts those values as a fallback; that URL fallback does not carry files. Use the installed PWA's system Share action to include files.
In Chats, choose a recent conversation or an employee. Choosing an employee resolves or creates a direct conversation and sends the message there. In Tasks, search for and select a task; the material is added as that task's comment.
Recipient selection and message contents
The page loads up to 12 recent conversations and up to 12 tasks per request. Only active employees are shown; employee search displays the first 12 matches, while the locally stored frequent-employee section contains up to five entries for this browser. These are suggestions, not a separate access list: every destination still uses the portal's normal permissions.
The sent body is assembled in this order: your note, the source text, and the URL, with each non-empty part on its own line. The source title is shown in the preview and prefilled as the initial note; it is not added a second time unless it remains in the note field.
Content that can be sent
The PWA manifest accepts images, video, PDF, and plain-text files, but the browser may limit file type, size, or count. Review each file's name and contents before sending. An empty or unreadable queue requires sharing again. The send button stays disabled until a destination is selected. Files upload before the message or comment is created. If upload or send fails, the queued payload is not considered complete: check connectivity, your signed-in session, and permissions before retrying. A retry can upload the files again, so check whether the first message or comment appeared before retrying to avoid duplicates.
Errors and security
An active signed-in session is required. Conversation, employee, and task lists and the final send still use your normal read/write permissions; sign in again or choose an accessible destination if the session expired or access was denied. Sharing does not expand access rights. Recipients see only what their chat or task permissions allow. Never share passwords, tokens, private client files, or secret-bearing links.
Related sections