Aircraft Management Settings

Aircraft documents are organised into a nested folder system. Each folder can contain:

• Subfolders: Additional folders to group related documents.
• Document templates: Definitions of the types of documents that can be uploaded (e.g., Certificate of Registration, Insurance Certificate).

Document templates define properties such as validity period, whether the document is optional, and which aircraft or aircraft types the document applies to. When users upload actual documents to an aircraft record, they select from these templates.

Two radio button views control what you see:

• Active: Shows folders and document templates currently in use. These appear when managing aircraft documents.
• Deactivated: Shows folders and templates removed from active use. Deactivated items no longer appear in aircraft document management but remain for historical records.

Switching views updates the display immediately. Each view has expand/collapse controls to manage the folder hierarchy.

In the Active view, click the Add New Folder button (top-right) to create a top-level folder. The window opens with a form:

• Name: Enter a descriptive folder name (e.g., "Airworthiness Certificates", "Insurance Documents"). This field is required.

Click Submit to save. The new folder appears at the bottom of the Active list. You can add subfolders by expanding the folder and using the add subfolder action within it.

Cancel closes the window without saving changes.

The Active table shows a hierarchical tree of folders and document templates. Each row displays:

• Expand/collapse: Click the + or - button to expand or collapse nested items. Top-level controls expand or collapse all items at once.
• Name: The folder or document template name, indented to show hierarchy level.
• Applies to: Shows which aircraft or aircraft types the document template applies to (only for document templates).
• Optional: Indicates if the document is optional or required (only for document templates).
• Validity: Shows the validity period in days for documents (only for document templates).
• Deactivate: Red button with a ban icon that removes the folder or template from active use.

Each row also has edit actions (pencil icon) to modify folder names or document template properties.

Document templates define the document types that can be uploaded for aircraft. When editing a template, you can configure:

• Name: The document type name shown when uploading documents.
• Validity period: Number of days before the document expires and needs renewal.
• Optional: Whether the document is required or optional for aircraft.
• Applies to: Specific aircraft or aircraft types that require this document. Leave blank to apply to all aircraft.

Changes to document templates affect all aircraft using that template. The system does not automatically update existing documents when you change validity periods or applicability rules.

Engine positions are simple text labels that identify where engines are mounted on an aircraft. Common examples include:

• Left and Right for twin-engine aircraft
• Left, Centre, and Right for tri-engine aircraft
• Inboard Left, Outboard Left, Inboard Right, Outboard Right for four-engine aircraft

Once defined, these labels are used when assigning engines to aircraft types and tracking engine-specific information.

A search box (top-left) filters engine positions by name as you type. An information icon next to the search box shows which fields are searchable.

If no results match your search, an alert displays: "No results found."

Click the Add engine position button (top-right) to open the engine position window. The window shows a simple form:

• Name: Enter a descriptive label for the engine position (e.g., "Left", "Centre", "Inboard Right"). This field is required.

Click Submit to save the new position. The system validates that the name is not empty. While submitting, the button shows a loading indicator with text "Submitting..."

Cancel closes the window without saving. New positions are added to the bottom of the list.

The engine positions table displays all defined positions in custom sort order. Each row shows:

• Sort arrows: Move the position up or down in the list. The top item has only a down arrow; the bottom item has only an up arrow. Items in the middle have both arrows.
• Edit: Opens the engine position window with the current name pre-filled.
• Name: The position label displayed throughout the system.

Sorting: Click the up/down arrows to reorder positions. The order determines how positions appear in dropdowns when assigning engines to aircraft types.

If no engine positions exist, the table displays: "There are no engine positions."

To edit a position name, click the edit button (pencil icon) in the row. The engine position window opens with the current name pre-filled. Make your changes and click Submit.

Musket sends email notifications to subscribed users and roles when:

• An aircraft document is approaching its expiry date (based on the validity period defined in the document template)
• An aircraft document has expired
• A new aircraft document is uploaded or an existing document is updated

Users can be subscribed to notifications in two ways: directly (individual user assignment) or indirectly through role membership (if their role is subscribed).

The table shows all users who are subscribed to aircraft document notifications, either directly or through role membership. The table includes:

• User name: The full name of the user. Click the column header to sort alphabetically.
• Direct user assignment: A checkmark (green) or cross (red) showing whether this user is directly subscribed to notifications.
• Remove/add direct assignment: A button to toggle the direct subscription on or off. Green (+) to add, red (-) to remove.
• Role assignment columns: One column for each subscribed role, showing a checkmark (green) if the user has that role or a cross (red) if they don't.

Users receive notifications if they have a direct assignment or belong to at least one subscribed role. The table only shows users who meet at least one of these conditions.

A search box (top-left) filters the user table by name, identification number, passport number, or email as you type. An information icon next to the search box shows which fields are searchable.

The search applies only to users who are already subscribed or belong to subscribed roles. It does not search all users in the system.

To directly subscribe a user to notifications:

1. Click the Add user button in the bottom-left of the table.
2. In the window that opens, use the user search to find and select the user. Only users who are not already directly subscribed appear in the dropdown.
3. Click Submit to save. The user is added to the table with direct assignment enabled.

If you try to submit without selecting a user, an error message displays: "Must select a user."

Cancel closes the window without changes.

To remove a user's direct subscription:

1. Find the user's row in the table.
2. Click the red (-) button in the "Remove/add direct assignment" column.
3. The user's direct assignment is immediately toggled off.

If the user still appears in the table after removing direct assignment, they remain subscribed through one or more role memberships. To fully unsubscribe them, either remove them from those roles or unsubscribe the roles from notifications.

To subscribe all users in a role to notifications:

1. Click the Add role button in the top-right of the table (in the "Role assignments" section).
2. In the window that opens, select a role from the dropdown. Only roles not already subscribed appear in the list.
3. Click Submit to save. A new column is added to the table for this role.

All users with this role will now see a checkmark in the new role column and will receive notifications.

If you try to submit without selecting a role, an error message displays: "Must select a role."

To unsubscribe all users in a role:

1. Find the role's column in the "Role assignments" section (it shows the role name in the header).
2. Click the red (-) button in the column header.
3. The role column is immediately removed from the table.

Users who previously received notifications through this role will still appear in the table if they have a direct assignment or belong to other subscribed roles. Otherwise, they disappear from the table entirely.