Rank Configuration
Rank Configuration defines the reference ranks that Crewlap uses in applications, vessels, positions, crewlists, and assignments.
Use this area when you need to maintain the global rank catalogue. These values are shared by the back office, so changes can affect several operational pages.
Rank Structure
Open Administration | Ranks to see the rank reference data.
The page is split into three sections:
Rates: high-level rate values used for grouping and sorting ranks.
Departments: departments or functional areas used to classify ranks.
Ranks: the actual rank values selected on applications, positions, assignments, and crew planning pages.
Each table can be filtered and sorted. Use the plus button in a section to create a new record, or open an existing row to edit it.
Rate
A rate record has:
Key: the stable technical key. It is entered during creation and should not be changed later.
Weight: the sorting weight. Lower or higher values affect ordering where rates are displayed.
Value translations: the visible label for each configured language.
Fill every language. If translations are not ready, repeat the same English label for all languages until proper translations are available.
Department
A department record has the same basic structure as a rate:
Key identifies the department.
Weight controls ordering.
Value translations provide the visible name.
Departments are selected when a rank is created or edited.
Rank
A rank record connects a visible rank name to a department and a rate.
The form includes:
Department: the department this rank belongs to.
Rate: the rate this rank belongs to.
Key: the stable rank key.
Weight: the sorting weight.
Value translations: the visible rank name in each language.
Ranks are used by vessel positions, seafarer applications, assignments, and crewlist planning. Change rank names carefully because users may already recognize existing labels in daily work.
Saving Changes
Click Save after editing a rate, department, or rank.
If a validation message appears, fix the highlighted field and save again. Typical causes are a missing required selection, an empty key during creation, or a missing required label.
Good Practice
Keep keys short and stable.
Use clear names that match the terminology used by crewing teams.
Prefer changing labels over creating duplicate ranks with nearly the same meaning.
Check where a rank is already used before changing its business meaning.