Skip to content

Signing in, and where you are

Shipbuilder runs in a browser and asks for a username and a password.

The Shipbuilder sign-in page: the logo, a Username field, a Password field and a Sign in button.
The sign-in page. Your username is normally your e-mail address, in lower case.

The sign-in page. Your username is normally your e-mail address, in lower case.

Where it brings you

Signing in opens the application on the workspace you had open last. The first time there is none, and the page says so:

The application after a first sign-in: a nearly empty page with the workspace selector in the top right reading Select workspace.
No workspace chosen yet. Everything else waits for the selector.

No workspace chosen yet. Everything else waits for the selector.

Choosing a workspace

A workspace is one project: its own documents, its own spaces, its own history. The selector lists the workspaces you have been given access to, and you can type in it to find one by name.

The workspace selector dropdown open, listing several workspaces by name, each with an indented Client row underneath it.
Open the selector and pick a workspace. Type part of its name to narrow the list.

Open the selector and pick a workspace. Type part of its name to narrow the list.

Picking a workspace loads its menu and lands you on its Dashboard. From then on the selector shows the name of the workspace you are in — glance at it before you change anything, because two workspaces look identical apart from that name.

Portals: one workspace, several menus

Under a workspace the selector may show indented rows — Client, here. A portal is the same workspace through a different menu, arranged for one role: the Main portal is the yard’s full menu; the Client portal is what the owner gets — the register and the transmittals, read-only apart from the comments they may add. Switching portal changes what the menu offers, not what the data is.

The same workspace opened through its Client portal: a shorter menu with Dashboard, Documents, Comments and Transmittals, the selector reading the workspace name followed by Client, and the register shown read-only.
The Client portal of the same workspace: the selector says which portal you are in, the menu is the owner's, the records are the same.

The Client portal of the same workspace: the selector says which portal you are in, the menu is the owner's, the records are the same.

An environment is not a workspace

Two things in the top of the window tell you where you are, and they are easy to confuse.

The environment is the address in the browser’s bar. An installation comes in a pair — a test environment, updated continuously, and a production one, updated on Monday nights — and they are separate installations with separate data. The screens are identical, which is exactly the problem.

The workspace is the selector in the top right. Same environment, different project.

The account menu

Your initials, top right, open it.

The account menu: a name, an e-mail address and a role tag, a theme switch offering System, Light and Dark, then What's new, About and Log out.
The account menu — who you are signed in as, the theme, what changed, and the way out.

The account menu — who you are signed in as, the theme, what changed, and the way out.

  • Who you are — your name, your e-mail address and your role. Worth a glance when the application refuses you something: the answer is sometimes that you are signed in as somebody else, or with less than you thought.
  • The themeSystem, Light or Dark.
  • What’s new — the release notes, newest first. See Getting help for when they appear.
  • About — the version. Quote it when you report a problem.
  • Log out — which is here and nowhere else, and is the first thing people cannot find.