[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ft-b0naiw0dwUZ22qBq_IsYx0W2Z1CiVIi1Xyk0jQP6A":3,"$fFKpNWZVVYTBYE3vPJn_-n27owUoP9TxN8PTy0yh8W6Y":17,"shop-vat-rates":102},{"article":4},{"id":5,"slug":6,"title":7,"summary":8,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":14,"bodyMd":15,"legacy":16,"createdAt":14},"47957da9-8639-4832-9d76-3c5ed57fd9dc","navia-accounts-roles-profiles-and-screens","NAVIA accounts, roles, display profiles and your phone as a screen","Personal accounts that follow you to any NAVIA aircraft, the four roles and how ownership is established in LX Cloud, pilot in command, screen and login types, display profiles, and adding a phone or tablet as an extra screen.","public",true,"9d0897b6-42d0-4643-8ceb-e8a02ce4a854","navia","NAVIA","2026-09-10T11:36:59.718Z","NAVIA separates two things that older panels ran together: the aircraft, which belongs to whoever owns it, and the pilot, who belongs to nobody. The aircraft holds its configuration — polar, envelope, devices, screens. You hold your settings, your layouts, your waypoints and your flights, in an account that travels with you to any NAVIA-equipped aircraft in the world.\n\nThis article covers who is allowed to do what on board, how ownership is established and shared, how the system decides which pilot is in command, and how screens work — including the one in your pocket.\n\n## Your account, and what it carries\n\nAn account is created once, either from the login page of any NAVIA display or at LX Cloud on the web. From then on it carries your personal settings, your display layouts, your waypoint and airspace files and your flights. Sign in on a different aircraft and all of it arrives with you.\n\nThe login page offers two ways in:\n\n- **Sign in** — e-mail and password. Two checkboxes matter. `Remember me` stores your credentials on the Core for that screen, so from then on it logs you in automatically at power-on and you will not see the login page again until you log out. `Are you the primary pilot?` declares you pilot in command for this flight.\n- **Guest** — name, weight and e-mail, nothing else. Meant for passengers and for pilots without an account. A guest gets a fresh copy of the default settings, and nothing is uploaded to the cloud.\n\n## The four roles\n\nWhat you are allowed to do on a particular aircraft depends on your role on that aircraft, not on your account as such.\n\n| Role | What it means |\n|---|---|\n| Owner | The aircraft is registered to this account. Full access, including all aircraft settings. |\n| Admin | A user the owner has granted administrator rights. Same technical rights as the owner. |\n| Regular | Any other signed-in account: full personal settings, navigation and logbook, but no aircraft configuration. |\n| Guest | Signed in without an account — name and weight only. Personal settings are not saved to the cloud. |\n\nA Regular or Guest user does not see the owner-only menu entries at all. `Airplane Settings` and `Instruments` are simply absent, which is why an aircraft can be handed to a renting pilot with no risk to its configuration.\n\n## Ownership, sharing and flying somebody else's aircraft\n\n**Ownership lives in LX Cloud, not in the aircraft.** When the Core's serial number is registered to your account, the aircraft recognises you as the owner the moment you sign in — on any of its screens. There is no owner setting in the cockpit to get wrong.\n\nThat also makes sharing trivial. A partnership, a club or a syndicate is a matter of **granting roles to the other accounts in LX Cloud**; nothing needs configuring on board. Grant Admin to your co-owner and their rights are identical to yours; leave the rest of the club as Regular users and they get their own settings without being able to touch the aircraft's.\n\nSign in on an aircraft that is not registered to your account — a rented glider, a club machine — and you are simply a **Regular** user there. All your personal settings and layouts arrive with you, the aircraft's own configuration stays untouched, and you fly with your waypoints on somebody else's panel.\n\n## Pilot in command\n\nOne signed-in pilot at a time is the **pilot in command**. Three things follow from it: the PIC's name goes into the header of the recorded IGC flight, the PIC's waypoint and airspace files are the ones loaded for navigation, and in a two-seater the second pilot is recorded as crew.\n\nWhich pilot is PIC follows from the seat a screen belongs to — the station marked `Pilot in command` in weight and balance — and can be declared explicitly with the `Are you the primary pilot?` checkbox at login.\n\n> The PIC's waypoint and airspace files are the ones loaded for navigation. If the wrong pilot is marked as PIC, you are navigating with somebody else's files. Confirm it before launch, not after landing.\n\n## Screens: every display is a browser\n\nEvery browser that connects to the Core — panel display, phone, tablet, laptop — registers itself as a **screen** with its own identity, and appears from that moment in `Airplane Settings › Screen Management`. A screen keeps its identity across restarts, so each physical display is configured once and stays configured.\n\nTwo properties define what a screen is: its **Screen Type**, which is what it shows, and its **Login Type**, which is whose data it shows and whether it asks for a login.\n\n## Screen Types: Navigation and Widget\n\n- **Navigation** — the full glass-cockpit view: moving map with the navbox line along the bottom, widgets over the map, alerts, and the side drawer with the in-flight tools. This is the main display of the aircraft.\n- **Widget** — a full-screen grid of widgets and no map. Ideal for a second screen dedicated to instruments: a PFD, engine gauges, a variometer.\n\n## Login Types: User, System and Child\n\n| Login Type | Behaviour | Typical use |\n|---|---|---|\n| User | The screen belongs to a person. It shows the login page — or, once `Remember me` was ticked, logs that pilot in automatically at power-on. | The main display in front of each pilot. |\n| System | No login at all. The screen shows a widget layout stored with the aircraft, identical for every flight and every pilot. | An always-on instrument panel: engine gauges, PFD. |\n| Child | The screen waits for a pilot to sign in on its parent screen, then follows that pilot automatically — same account, no second login. Logs out when the parent logs out. | A second screen or a tablet extending the pilot's main display. |\n\nTwo rules when combining the two properties. A **System** screen is always a Widget screen; selecting System switches the Screen Type to Widget for you. A **Child** can only be a Widget screen, and its parent is chosen from the list of other screens under `Parent ID`.\n\nWith several auto-login screens on board, they sign themselves in one after another during power-up, so do not be alarmed when a second display takes a few extra moments to come alive.\n\n## Display Profiles: your layouts follow you\n\nEverything you arrange on a screen — widget layout, navbox line, map layers, aircraft symbol, widget columns — is stored in a **Display Profile**. Profiles belong to *you*, not to the screen. They are part of your personal settings, they synchronise to LX Cloud, and they follow you to any NAVIA-equipped aircraft. Step into a different glider, sign in, pick your profile, and the screens look exactly as they do at home.\n\nKeep several if it helps — one per aircraft type, or one per screen size. They are managed under `User Settings › Preferences › Manage Profiles`, where each profile has a name, an aircraft type and a screen type. Which profile a screen currently uses is chosen either there or on the screen's card in Screen Management, and unlike the rest of the screen configuration, **switching the active profile is allowed for every user**, not only the owner.\n\nSystem screens are the exception: they use a layout stored with the aircraft, so the panel the owner configured stays identical whoever flies.\n\n## Screen Management\n\n`Airplane Settings › Screen Management` lists every screen the Core has ever seen, each as a card carrying its **Screen Name** (give each display something meaningful — \"Panel 12\", \"Right seat 7\", \"Engine 4\"), its **Screen ID**, its **Screen Type** and **Login Type**, the **Parent ID** if it is a Child, and its current **Display Profile**.\n\n![NAVIA Screen Management with one card per screen](\u002Fsite\u002Fimg\u002Fkb\u002Fnavia-screen-management.webp)\n\nScreen Type, Login Type and Parent ID are owner and admin settings; a Regular user sees only their own screens and can change only the Display Profile — from `User Settings › Preferences › Manage Profiles`, since Airplane Settings is not shown to them. When several screens are installed and you have lost track of which is which, press `Identify` on a card: the corresponding physical display briefly shows its name and ID full-screen.\n\n## Using your phone or tablet as a screen\n\nBecause displays are just browsers, adding one takes a minute.\n\n1. Open `Dashboard › Network › Wi-Fi Access Point` on any existing screen. It shows the aircraft's own Wi-Fi network — the **NAVIA Access Point** — with a QR code labelled `Scan to Connect`.\n2. Scan the QR code with the phone or tablet, or join the shown Wi-Fi network manually.\n3. Open the browser on the device and navigate to the Core's address. The device registers itself and appears in Screen Management as a new screen.\n4. Configure it there: typically Screen Type `Widget` and Login Type `Child` with your main display as parent. The tablet then follows your login automatically, and you arrange widgets on it exactly as on any other screen.\n\n![The NAVIA Access Point page with its join QR code](\u002Fsite\u002Fimg\u002Fkb\u002Fnavia-network-ap.webp)\n\n![A phone configured as an additional Widget screen](\u002Fsite\u002Fimg\u002Fkb\u002Fnavia-phone-widget.webp)\n\n## Where to go next\n\n- Setting up the aircraft the accounts sign in to: [commissioning a new aircraft](\u002Fkb\u002Farticle\u002Fnavia-commissioning-a-new-aircraft).\n- What synchronises, when, and what happens with no internet: [NAVIA and LX Cloud](\u002Fkb\u002Farticle\u002Fnavia-cloud-sync-offline-and-flight-recording).\n- The hardware behind the screens: [NAVIA system architecture](\u002Fkb\u002Farticle\u002Fnavia-system-architecture) and the [NAVIA range](\u002Fnavia).\n- Screens behaving in ways this article does not explain: [NAVIA troubleshooting](\u002Fkb\u002Farticle\u002Fnavia-troubleshooting).\n",null,{"categories":18,"articles":45,"search":101},[19,25,28,34,39],{"id":20,"slug":21,"name":22,"description":16,"sortOrder":23,"articleCount":24},"42232637-6088-4100-9314-0b4986098818","getting-started","Getting started",20,7,{"id":11,"slug":12,"name":13,"description":16,"sortOrder":26,"articleCount":27},25,10,{"id":29,"slug":30,"name":31,"description":16,"sortOrder":32,"articleCount":33},"92b87517-c814-4237-b180-19df9cb80b16","connectivity","Connectivity",30,3,{"id":35,"slug":36,"name":37,"description":16,"sortOrder":32,"articleCount":38},"db776f9a-4f67-42bf-94bc-171c93f10cea","service-repairs","Service & repairs",1,{"id":40,"slug":41,"name":42,"description":16,"sortOrder":43,"articleCount":44},"48e22b59-26c1-477f-b136-3d3728b6dc22","device-guides","Device guides",40,12,[46,52,58,59,65,71,77,83,89,95],{"id":47,"slug":48,"title":49,"summary":50,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":51},"edb2d23e-9cd8-48c9-abbc-365420c26247","navia-system-architecture","NAVIA system architecture: how the pieces fit together","Hub, Core, Sense, Displays, Traffic, UPS, EMU and Grip — what each unit does, how power and data flow over one cable per device, and how to plan a system before ordering.","2026-09-10T11:36:59.617Z",{"id":53,"slug":54,"title":55,"summary":56,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":57},"2e027321-055d-4b7a-9c2a-9c5036e8cc62","navia-commissioning-a-new-aircraft","NAVIA: commissioning a new aircraft","The thirteen steps from wired hardware to a configured aircraft: registering the Core to your account, aircraft identity and configurations, the polar, flight envelope and flaps, weight and balance, and the checks before the first flight.","2026-09-10T11:36:59.710Z",{"id":5,"slug":6,"title":7,"summary":8,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":14},{"id":60,"slug":61,"title":62,"summary":63,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":64},"941c6fbe-cc2a-4bc7-b698-4bcffbf8475f","navia-cloud-sync-offline-and-flight-recording","NAVIA and LX Cloud: synchronisation, working offline, flight recording and the logbook","What belongs to you and what belongs to the aircraft, when synchronisation runs and why it never runs in flight, flying with no internet at all, and how a recorded flight reaches the logbook and the cloud.","2026-09-10T11:36:59.724Z",{"id":66,"slug":67,"title":68,"summary":69,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":70},"51cc50eb-1866-421f-a066-d67a90faa095","navia-updates-databases-and-remote-support","Updating NAVIA: Core, ecosystem devices, databases and remote support","The update page and its three channels, reverting a version, why connected devices update themselves from the Core, keeping airspace and charts current, and the remote-support switch that stays off until you turn it on.","2026-09-10T11:36:59.734Z",{"id":72,"slug":73,"title":74,"summary":75,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":76},"e9e61fe3-3e10-4cc7-98a3-52450b11f313","navia-troubleshooting","NAVIA troubleshooting: warnings, alarms and status-bar items","What each status-bar item reports, the full list of warnings and alarms with what triggers them, and a symptom-cause-fix table for the sixteen things most likely to puzzle you — several of which are not faults.","2026-09-10T11:36:59.745Z",{"id":78,"slug":79,"title":80,"summary":81,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":82},"7698e2e3-2195-4b46-8ca3-2067e17da186","navia-emu-sensor-installation","NAVIA EMU: installing CHT, EGT, RPM, fuel-flow and fuel-quantity sensors","The thermocouple rules that govern everything, where CHT and EGT probes go and where they must not, RTD and pressure senders, fuel quantity and flow, RPM pickups, and two worked engine examples.","2026-09-10T11:36:59.755Z",{"id":84,"slug":85,"title":86,"summary":87,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":88},"43d23b57-4681-4d80-9aad-ba64fd471812","navia-emu-alerts-fuel-computer-and-logbook","NAVIA EMU in use: master warning and caution, the fuel computer, calibration and the engine logbook","How the annunciators behave and what acknowledging one does, what a missing reading means in flight, the fuel computer and its limits, calibrating a tank point by point, and why the factory thresholds are not your engine limits.","2026-09-10T11:36:59.779Z",{"id":90,"slug":91,"title":92,"summary":93,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":94},"af207643-1be9-46af-9613-c1cf9fb9c1a8","navia-sense-igc-recorder-and-calibration","NAVIA Sense: the IGC recorder, calibration and the compass swing","The integrated IGC recorder and its security seal, engine noise and when an external means-of-propulsion sensor is required, the Certificate of Calibration that replaced the barochart, and a compass that calibrates itself in flight.","2026-09-10T11:36:59.793Z",{"id":96,"slug":97,"title":98,"summary":99,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":100},"6d3a78b9-2140-4bf8-ba3e-164ddf82b29c","navia-traffic-setup-and-firmware","NAVIA Traffic: FLARM\u002FADS-B setup, firmware modules and the range analyser","Two modules updated separately, why obstacle databases and licence files are tied to your serial number, configuring the unit from its portal, connecting it to a Core Pro, and reading the range analyser honestly.","2026-09-10T11:36:59.803Z",false,{"AT":23,"BE":103,"BG":23,"CY":104,"CZ":103,"DE":104,"DK":26,"EE":105,"ES":103,"FI":106,"FR":23,"GR":106,"HR":26,"HU":107,"IE":108,"IT":105,"LT":103,"LU":109,"LV":103,"MT":110,"NL":103,"PL":108,"PT":108,"RO":104,"SE":26,"SI":105,"SK":23},21,19,22,24,27,23,17,18]