Skip to guide content
WavelinkWAVELINKAJ OFFSHORE SOLUTIONS · HELP
Help centreVessels & shipments

CORE GUIDE TOPIC · fleetaccess

About these instructions

This reader standardises presentation, not the entire procedure library. The original instructions, version labels and warnings are retained. Some topics describe the local Windows hub or earlier interface labels. They must not be read as proof that all desktop setup, imports or recovery work is available in the hosted browser.

The full wording, hosted/local scope, native Help and PDF review remains on the development list. Use only company-approved operational procedures; viewing Help does not approve a checklist, release equipment or verify work.

On this page 2 sections
  1. Understand the access models
  2. Shipments involving another site

User instructions

Set vessel-only access

Explicit site roles without project-wide access

  1. Create the person as an enabled, named non-administrator account in Users & access. Existing passwords continue to work.
  2. In Fleet & manifests → User vessel access, select the account. In the browser, use Access & setup → Edit access.
  3. Choose Vessel-only access, then select a role for each permitted site. Leave other sites at No access.
  4. Review the access warning, enter a reason and save. Saving revokes the person’s current sessions. They must sign in again through /fleet.
RoleAvailable actions
ViewerView permitted site assets, relevant shipment records, files, reports and planned shipment dates.
OperatorViewer access plus prepare at the origin, confirm dispatch, receive at the destination, record physical returns at the origin, and attach shipment evidence.
ManagerOperator access plus close a fully received/returned manifest and record an authorised quarantine release at that site.
Project administratorManage every site, access grant and initial allocation in this project, and retain full project access and exports. A site Manager is not a project administrator.

For operational logs, separately grant Log permissions. Read Set vessel log permissions; logistics roles do not open logbooks automatically.

Understand the access models

Project workspace access keeps the earlier project-wide permissions. Vessel-only access blocks those screens and permits granted logistics sites and separately enabled logbooks. Switching back restores the broader project profile. Preserve earlier device-only work before changing access.

The same checks protect the portal’s lists, guessed links, asset evidence files, shipment reports and calendar results. Vessel-only accounts cannot obtain a full project backup or enter the Windows Admin console. Department membership and Supervisor status do not bypass the restriction.

Shipments involving another site

Preparing a new manifest requires Operator or Manager access at its origin and at least Viewer access at the destination. The recipient needs destination Operator or Manager access to receive an existing manifest. A source-only operator can dispatch a prepared authorised manifest; a destination-only operator can receive it.

A sender or recipient can see the shipment route and line snapshots, not the other site’s unrelated work. Both sides may inspect shipped assets in transit. After receipt, current asset access follows the destination; the sender keeps the shipping snapshot, not future asset records.