Core Setup

Who does this: System Administrator

Global Settings is the first place to visit. It controls company-wide configuration that everything else depends on.

• Company Settings — confirm your company name, registration details, and logo.
• Active Countries — add the countries your operation uses. These drive availability throughout the system (airport lookups, fee structures, etc.).
• Currencies — set your default currency. This is the base currency for all quoting and reporting.
• Exchange Rates — add initial exchange rates for every currency you operate in. Recommended: Establish a regular procedure to update rates (e.g. monthly) if you quote or invoice in multiple currencies. Stale rates will affect quote accuracy.
• EFB Settings — review the default Musket App (EFB) settings. These control what pilots see and can interact with in the mobile app.
• API Access — if you plan to connect external systems to Musket via API, keys are managed here. See Integrations for details.

Full details: Global Settings

Who does this: System Administrator

Roles control what users can see and do in Musket. Before adding your team, set up the roles they'll be assigned.

• System roles are built into Musket and unlock specific capabilities (e.g. Flight Deck Crew enables endorsements and flight rostering). You cannot rename or delete system roles.
• Custom roles are created by you, for your own grouping and access control needs.
• Recommended: Keep your roles list as short as possible. Only create a new role if it genuinely needs different access or filtering from existing roles. Long role lists make user management cumbersome over time.

Full details: System Roles  |  Create a Role  |  Role Management

Who does this: System Administrator

There are two ways to get users into Musket:

• Recommended — Self-registration: Share your Musket URL with staff. Ask them to self-register using the Register link on the login page. Once registered, an administrator:
  1. Assigns the correct role(s) to the user.
  2. Approves the registration.
  3. Optionally edits the profile to fill in additional details (position, base, etc.).
• Alternative — Manual add: Go to Administration → User Management and add users directly. The user receives an email invitation to set their password, then logs in and can complete their own profile.

Once a user is in the system — regardless of which path — they are immediately available across all of Musket, including the Crew & Staff Register.

Full details: Approve Registrations  |  Add a User  |  Assign Roles  |  User Management

Who does this: System Administrator

Bases represent your operational locations — home bases, outstations, or administrative offices. Aircraft, staff, and operations can all be associated with a base.

• Add all locations relevant to your operation.
• Bases are used to associate staff with locations, and are selectable across the system — for example on reports, audits, and other operational records.

Full details: Create a Base  |  Organisation Bases

Who does this: System Administrator / Chief Pilot / Maintenance Manager

Aircraft Types are the most foundational data item in Musket. They must be added before aircraft registrations, scheduling, quoting, or maintenance tracking can be configured.

• Performance data — speeds, ranges, and weights used for quote calculations.
• Crew configurations — how many flight deck crew and cabin crew this aircraft type requires.
• Weight & Balance — centre of gravity envelopes and loading configuration.
• Flight Data Fields — this step is important and often overlooked:
  • These fields define what pilots can complete in the Musket App (EFB) after each flight (block times, fuel, landings, etc.).
  • They also define what data can be captured in Post-Flight Actuals (PFA) in the scheduling module.
  • If you are using Musket to track maintenance hours automatically — the hours source (typically Block Hours or Air Time) must be configured here. Without this, maintenance tracking via PFA will not work.

Full details: Add an Aircraft Type  |  Weight & Balance  |  Aircraft Types — Aircraft Management  |  Aircraft Types — Maintenance Hub

Who does this: System Administrator

Once Aircraft Types are in place, add your actual aircraft — each with its registration and linked to its type.

• Add each registration individually and select its Aircraft Type.
• Assign each aircraft to a base (if applicable).
• Additional details (serial numbers, colour, images) can be completed now or at any point.

Full details: Add an Aircraft  |  Fleet Management

Who does this: System Administrator

Review the Aircraft Management settings before staff start uploading aircraft documents.

• Document folder structure — define the folder categories used to organise aircraft documents (e.g. Airworthiness, Insurance, Manuals). All aircraft share this structure.
• Engine & propeller labels — label your engine positions (Engine 1, Engine 2, Port Engine, etc.) to match your operational terminology.
• Notification expiry settings — configure how early Musket should alert you before aircraft documents or items expire.

Full details: Document Folder Structure  |  Engine & Propeller Labels  |  Notification Expiry Settings  |  Aircraft Management Settings

Who does this: System Administrator / Chief Pilot / Cabin Crew Manager

Staff Management Settings control the structure of your crew records. Set up the basics now — detailed crew & flight operations configuration is covered in Crew & Scheduling Setup.

• Crew Positions — define the positions used when assigning crew to flights (e.g. Captain, First Officer, Training Captain). Keep this list short. Full guidance: Crew & Scheduling Setup → Flight Crew Positions.
• Licence & Document Types — define the categories of compliance documents your staff must hold (medicals, licences, training records, etc.).
• Recency Document Folder Structure — set up the folder categories for staff compliance documents. This must be in place before staff can upload their licences and records.
• Non-Flight Duties — define duty period types that are not flights (e.g. Simulator, Ground Duty, Standby).

Full details: Compliance Documents Structure  |  Non-Flight Duties  |  Staff Management Settings

Who does this: System Administrator / Document Controller

Once your team is added, you can begin uploading company manuals, procedures, and policies to the Document Library for staff to access. This is an ongoing task rather than a one-time setup step — but if you have documents ready, it's a good time to start.

Full details: Document Control — Manage Library

Core Setup is now complete. Your system has the foundational structure in place. Continue with the remaining setup areas — work through them in the order that best matches your operation's priorities:

• Crew & Scheduling Setup — pilots, endorsements, FDP regulations, scheduling configuration
• QMS & SMS Setup — safety, quality, security, and DG management systems
• Maintenance Setup — maintenance tracking, MEL, technical directives
• Commercial Setup — quoting, fees, clients, invoicing
• Data Imports — import historical data from previous systems
• Integrations — connect with third-party systems and booking platforms