Overview

SeaSquad CMS is a crew-management platform for ship operators. It gives a manning or crewing department one place to hold seafarer records, plan who sails on which vessel, run recruitment, and keep the crew office and the fleet in sync — while also giving individual seafarers and job applicants their own self-service access to the parts of the system that concern them.

Who it's for

The product serves three distinct audiences, and each gets its own purpose-built interface rather than a single interface with role toggles:

• Crewing and manning staff — the office team that maintains the crew register, plans vessel manning, and runs recruitment from application to hire.
• Serving seafarers — crew members who need to see their own record and documents without going through the office for routine questions.
• Job applicants — candidates applying to open positions, from outside the organization, with no prior account.

The three zones

SeaSquad CMS is delivered as three separate, purpose-built experiences:

Office console. The working environment for crewing and manning staff. This is where crew records are maintained, vessels and manning requirements are managed, recruitment pipelines are run, and day-to-day crewing decisions are made. Access is role-based — see Roles and permissions.

Seafarer self-service portal. A dedicated, restricted view for serving crew. A seafarer signs in and sees only their own record: personal details and the documents held on file for them. There is no visibility into other seafarers, vessels, or office-only data — access is scoped to the individual, not granted through a role.

Public careers site. The recruitment front door. Job openings are listed publicly, and a candidate can sign up, browse openings, and submit an application with supporting documents — no invitation or prior relationship with the operator required.

How the zones relate

The office console is where records originate and are maintained. A hire made through the careers pipeline brings an applicant's submitted documents and details into the crew register as a new crew record. Once someone is on the register, their seafarer self-service login is issued by the office — seafarers cannot self-register. This keeps a clear boundary: only the office can add someone to the crew register or grant portal access, but once granted, a seafarer manages their own day-to-day visibility into their record independently.

Deployment model

Each client organization runs its own isolated instance of SeaSquad CMS — its own environment, its own data, and its own branding (product name, tagline, and colors). Nothing is shared or visible across instances. This means an operator's crew data, recruitment pipeline, and vessel information stay entirely within their own deployment.

Where to go next

• Crew management — seafarer records, documents, and employment lifecycle status.
• Fleet and manning — the vessel register, rank structure, and manning planning.
• Roles and permissions — who in the office can do what.
• Notifications — how crewing events reach the people who need to know about them.