All guides

Getting started with MyBoatDesk

A clean foundation makes later maintenance, documents and exports much easier.

Before you begin

  • Access to the registration email
  • Basic boat details and its time zone
  1. 1

    Verify your email

    Open the link in the registration email before using the protected product areas.

  2. 2

    Create your boat

    Add its name, type, build year, time zone and operating mode. You can extend these details later.

  3. 3

    Choose modules

    Enable the areas you use. Disabling a module later hides the capability but never deletes its records.

  4. 4

    Add equipment and documents

    Create the central components first, then connect manuals, invoices and maintenance plans.

Check the result

Setup is dependable when the boat is visible, key components have unambiguous names and the first documents open from the correct object. Review “Getting started with MyBoatDesk” once from another crew member’s perspective: labels, status and the next action should make sense without a verbal explanation.

If something goes wrong

If the confirmation email is missing, check spam and the address spelling. Avoid creating a second account while support can still trace the first registration.

Keep data safe and traceable

For “Getting started with MyBoatDesk”, capture only information required for the task. Passwords, access tokens and complete payment details never belong in notes or screenshots. Every change should remain connected to the correct boat, a responsible person and a visible status. If two devices produce different versions, resolve the conflict deliberately; an earlier accepted record must not disappear without explanation.

After the first real use

After the first use, review the workflow against “Verify your email”, “Create your boat”, “Choose modules”, “Add equipment and documents”. Add missing labels, sources or follow-up work in context. A short review at season change, after a crew change or when signing in on a new device is then enough. The guide remains useful without maintaining the same task in parallel private lists.