Skip to guide content
WavelinkWAVELINKAJ OFFSHORE SOLUTIONS · HELP
UI 07Open workspace
Help centreVessels & shipments

CORE GUIDE TOPIC · fleet

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 6 sections
  1. Open the integrated workspace
  2. Set up sites deliberately
  3. Grant the appropriate access
  4. Find equipment and evidence
  5. Protect unfinished forms
  6. Keep project and network boundaries

Wavelink 1.34.10 / workspace continuity

Manage vessels and shore bases

A controlled logistics workspace within the selected project.

Open the integrated workspace

Choose Fleet & vessels in the browser sidebar. Vessels, manifests, receiving, assets, logbooks, issues, calendar and setup stay under the same main header and valid login. The standalone /fleet bookmark remains available and may require its own sign-in; normal main-workspace navigation does not use that separate page. Desktop Admin keeps Operations > Fleet & manifests.

Set up sites deliberately

A project administrator uses Vessels & bases > Add vessel / base for vessels, shore bases, warehouses or workshops. Record the verified name, type and optional site details. Allocate existing stock only after confirming its physical site; boxes include active nested contents. Enter a reason. Initial allocation is not inferred from item names; later site changes use a manifest.

Grant the appropriate access

Use Access & setup for vessel grants. Site names, inventory locations, departments and Supervisor status do not grant vessel access automatically. Logbooks and Assigned issues need separately granted vessel-log permissions. Vessel-only accounts remain restricted to their authorised logistics and enabled logbooks, not older project-wide workspaces. Test sender and receiver access with fictional records first.

Find equipment and evidence

Assets & transit shows permitted equipment, shipments, images, box contents, certificates and linked maintenance. A multi-asset certificate requires access to every linked asset. Recorded site custody is separate from ownership and department custody. Dispatch makes equipment In transit; it does not create a second destination copy. Review confidential document contents before sharing.

Protect unfinished forms

An open Fleet form blocks leaving for another workspace until saved or closed. Lists and filters are retained while the main page remains open. Session expiry requires main sign-in; only the same account can resume its open in-memory form. Nothing is automatically saved by navigating or signing in. Fleet still needs a reachable hub and does not have a new offline draft queue.

Keep project and network boundaries

All sites belong to this project database. Separate databases are not combined or synchronised; imports have a new hub identity. Current custody determines supported asset access; downloaded copies cannot be recalled. Existing accounts and backend permissions still control access. Keep the approved private network; this release adds no public hosting, cloud sync or network repair.

Browse all Help topicsBack to topic start ↑