The crew-facing side of Joya. Crew see their own roster, the flights they are on,
and file the journey log from the aircraft.
Crew sign in with the same account they would use on the web — their login
or work email and password, plus a one-time code if your airline has
OTP enabled.
A deactivated account cannot sign in. See Users.
Their roster — duties and flights, as published. Drafts are not visible;
a roster appears only once it is published from the
event calendar.
Their flights — the legs they are crewed on, with times and route.
Other crew on the flight — subject to
crew access, which controls whose names a given position
may see. Where a name is not permitted, the app shows Access Denied in its
place.
Crew complete the journey log from the app: block times,
fuel, counts, pilot flying and notes.
Which fields appear, and which are mandatory, is decided by your operator in
journey log fields.
Crew have a limited number of edits. Once used, the form locks and shows
how many were used. Ops staff can still complete or correct it from the web.
If your operator uses push, crew receive notifications for roster changes,
reminders and broadcasts. These are configured in
push settings; the message
wording comes from the templates there.
Push arrives only on devices where the crew member has allowed notifications and
signed in at least once.
| Symptom | Cause | Fix |
|---|---|---|
| Roster is empty | It has not been published | Publish from the event calendar |
| All colleagues show "Access Denied" | No crew-access rule for their position | Add one — see crew access |
| Cannot edit the journey log | Edit quota used, or no edit rights | Ops can complete it |
| No push notifications | Permission denied on the device, or push not configured | Re-enable notifications; check push settings |
| A newly enabled journey-log field is missing | The app is showing a cached form | Reopen the app |