When you share a voyage, cargo, or port call, the recipient sees it in the Veson Platform. This article lists what the recipient sees on each document type, section by section.
Key Points
-
Commercial terms are visible. Recipients of a shared voyage or cargo can expand the cargo details and see the freight rate, demurrage rate, laytime allowed, and NOR offset.
-
Recipients can't share onward or see mail. The Sharing and Related Mail panels appear only for the company that owns the document.
-
Linked records aren't shared automatically. Invoices and attachments appear for the recipient only if you add them as part of the share. Your forms aren't shared with the document.
-
Some sections use vessel tracking data. The map, berth stays, and port activities come from vessel tracking, not from your IMOS data.
At a Glance
|
Page |
Section |
Voyage |
Cargo |
Port Call |
|---|---|---|---|---|
|
Main page |
Overview |
✅ Shown |
✅ Shown |
✅ Shown |
|
Map |
✅ Shown |
✅ Shown |
— |
|
|
Itinerary |
✅ Shown |
✅ Shown |
— |
|
|
Cargoes/Cargo Handlings |
✅ Shown |
— |
✅ Shown |
|
|
Bunkers |
Partial |
— |
— |
|
|
Port Agents |
— |
— |
✅ Shown |
|
|
Vessel Details |
— |
— |
✅ Shown |
|
|
Port Activities |
— |
— |
✅ Shown |
|
|
Invoices |
If shared |
— |
If shared |
|
|
P&L |
❌ Hidden |
— |
— |
|
|
Claims |
❌ Hidden |
❌ Hidden |
— |
|
|
Sustainability |
❌ Hidden |
— |
— |
|
|
Side panels |
Sharing |
❌ Hidden |
❌ Hidden |
❌ Hidden |
|
Related Mail |
❌ Hidden |
❌ Hidden |
— |
|
|
Attachments |
If shared |
If shared |
— |
|
|
Forms |
Own forms only |
— |
Own forms only |
The dash (—) means the section doesn’t exist on that document type for anyone, owner or recipient.
Voyage
|
Section |
Status |
What the Recipient Sees |
Notes |
|---|---|---|---|
|
Overview |
✅ Shown |
Vessel name and voyage no., voyage status, cargo summary (quantity, grade, charterer/owner), progress bar from first load to last discharge, next ETA/ETB, operator, last updated, and Shared By with your company name |
|
|
Map |
✅ Shown |
Vessel position and route |
Position comes from vessel tracking. |
|
Itinerary |
✅ Shown |
Port and country flag, port function (for example, L, D, F), arrival and departure (actual or ETA), At Sea marker, passing points, berth stays |
Berth stays come from vessel tracking, not your berth data. |
|
Cargoes |
✅ Shown |
Quantity, grade, and cargo ID; status; CP date; laycan; charterer/owner; BL quantity |
Expandable details: freight rate, demurrage rate, freight type, option type, NOR offset, laytime allowed, vessel type, voyage, COA (if any), FOB flag (if any), terms. The Buy/Sell label is removed because it reflects your side of the deal. |
|
Bunkers |
Partial |
ROB chart and table (arrival and departure by fuel), port consumption, consumption by leg, days, distance, and ballast/laden |
Opr Qty and Req Qty are blank. Operational quantity, price, and bunker requirements aren't included in the share. |
|
Invoices |
If shared |
Invoices you added to the share |
The heading appears if invoices are linked to the voyage, but the list is empty unless you added them when you shared. |
|
P&L |
❌ Hidden |
— |
P&L data isn't part of the share. |
|
Claims |
❌ Hidden |
— |
|
|
Sustainability |
❌ Hidden |
— |
|
The dash (—) means the section doesn’t exist on that document type for anyone, owner or recipient.
Cargo
|
Section |
Status |
What the Recipient Sees |
Notes |
|---|---|---|---|
|
Overview |
✅ Shown |
Vessel and voyage no. (or FOB Voyage or [Vessel TBN]); quantity, grade, and cargo ID; status; progress bar; CP date; laycan; charterer/owner; BL quantity; next ETA/ETB; operator; Shared By with your company name |
Expandable details: the same commercial terms as a voyage's cargo (see Voyage above). Related Cargoes (collapsed by default) lists other cargoes on the same voyage that the recipient can see. The Buy/Sell label is removed. |
|
Map |
✅ Shown |
Vessel position and route |
Position comes from vessel tracking. |
|
Itinerary |
✅ Shown |
Load and discharge ports for this cargo, arrival and departure, View Deal Chain toggle (when available), last updated |
Passing points aren't shown. |
|
Claims |
❌ Hidden |
— |
|
The dash (—) means the section doesn’t exist on that document type for anyone, owner or recipient.
Port Call
|
Section |
Status |
What the Recipient Sees |
Notes |
|---|---|---|---|
|
Overview |
✅ Shown |
Port name and UN code, country and flag, port function, vessel, voyage no., ops coordinator (name and email), arrival, departure, last updated |
There's no Shared By line on port calls. Only the share icon appears. |
|
Cargo Handlings |
✅ Shown |
Cargo grade, load/discharge, nominated quantity, load port, discharge port, terms, liner terms, shipper, receiver |
|
|
Port Agents |
✅ Shown |
Agent company name, role, currency, phone, email |
|
|
Vessel Details |
✅ Shown |
Name, type, deadweight, year built, beam, laden speed, ballast speed |
|
|
Port Activities |
✅ Shown |
Timeline and map of the port call |
Built from vessel tracking data. Your IMOS port activities (for example, NOR or all fast) aren't shown here. |
|
Invoices |
If shared |
Invoices you added to the share |
Works the same as on a voyage. |
Side Panels
|
Panel |
Status |
What the Recipient Sees |
|---|---|---|
|
Sharing |
❌ Hidden |
Owner only. Recipients can't see who else the document is shared with, and they can't share it further. |
|
Related Mail |
❌ Hidden |
Owner only (voyages and cargoes). |
|
Attachments |
If shared |
Attachments aren't shared with the document automatically. A file appears only if you added it to the share. If no files were shared, the panel and its paperclip button don't appear. Recipients can view and download shared files, but can't upload, delete, or parse them. Voyages and cargoes only. |
|
Forms |
Own forms only |
Your forms aren't shared with the document. The recipient sees only forms their own company has sent against this voyage or port call, plus any forms shared with them separately. Recipients can start only the form types you've shared with them, and only if they have the required user permissions. The new form is addressed to you automatically. For example, this is how an agent sends a report against a shared port call. Voyages and port calls only. |