IndiGo pilots connect their roster by logging in to the airline's own eCrew page inside the Wingman Pilot Logbook app, on their phone — once. Wingman then imports the roster on its own, with no authenticator code to relay and nothing to re-enter. It replaces a server-side login that needed the pilot to type a code against a 30-second clock, and failed often. (Setup happens in the Wingman Pilot Logbook app; AirRoster inherits the connection but cannot create one.)

Steps

1. Update Wingman from the App Store or Play Store. This feature arrives with a store update, so an app that only refreshed itself in the background won't have it yet.

2. Open the Roster Import tab and tap Set up roster import (or Change airline if a roster is already connected).

   

3. Pick IndiGo from the airline list.

4. Tap "Connect IndiGo (on-device)". The screen explains it first: "Log in to IndiGo directly on your device — your password never leaves your phone."

   

5. Log in as you normally would with IndiGo — including the authenticator step. This is IndiGo's own sign-in page, opened inside the app; check the address bar. Take as long as you need: nothing is waiting on a timer.

   

6. Done. The browser closes by itself, Wingman shows "Connecting your roster…", and you land on the import screen — pick a date range and tap Fetch flights. Turn on Daily auto import from the Roster Import tab and your flights arrive on their own each morning.

7. Using AirRoster as well? There's nothing more to do there. As long as both apps use the same email, AirRoster picks up the connection you just made automatically — no second login, nothing to set up again. Note that the connection is always made in the Wingman Pilot Logbook app: it isn't available inside AirRoster. If you use AirRoster on its own, keep using the Microsoft Authenticator setup instead.

If IndiGo later ends the session, Wingman shows "Session expired — Reconnect to continue importing"; one tap reopens the same login page.

Frequently asked questions

Do I still need my authenticator every time I import? No. You use it once, when you connect — on your own phone, at your own pace. After that, imports run on their own.

Why did the old roster import keep failing? Because the login ran on our server while your authenticator code lived on your phone. The code had to be typed and relayed before it expired, and approval prompts had nobody to tap them. Now the login happens on your device, so there's no relay to fail.

Does Wingman see my IndiGo password? No. You type it into IndiGo's own login page (icrew.goindigo.in — check the address bar) inside the app. Wingman receives only the temporary session your login creates, which lets it read your roster and nothing else.

I use both Wingman and AirRoster. Do I connect twice? No — as long as both use the same email. Connect once in the Wingman Pilot Logbook app and AirRoster picks it up automatically.

Can I set this up from AirRoster instead? Not at the moment. The on-device connection lives in the Wingman Pilot Logbook app only. If you use AirRoster on its own, carry on with the Microsoft Authenticator setup — it still works exactly as before.

I changed my IndiGo password. Do I need to do anything? No. Wingman never stored it. Your existing connection keeps working; next time you reconnect you'll just use the new password on IndiGo's page.

Why do I sometimes have to reconnect? IndiGo eventually ends idle sessions. Wingman keeps yours alive in the background, but if the airline ends it you'll get a one-tap Reconnect prompt.

I don't see the option. Why? Make sure you're on the latest app from the App Store or Play Store (v1.0.74+) and using the phone app, not the web version. It's IndiGo-only for now.

Is this coming to other airlines? That's the plan. The approach works for any airline whose crew portal sessions can be used this way.

Draft generated from the internal feature guide by kb-publish.