Apps authentication
Apps authentication controls how employees sign in to the Leena AI mobile and desktop apps. It mirrors web authentication, with device-level options that only make sense on an installed app.

Where to find it
Open the Admin Console, then go to Leena Channels → Apps authentication.
Separate from browser accessThis page covers the installed apps only. Browser access is configured on Web authentication, and access rules that apply after sign-in live on Other auth settings.
The two can use different methods — SSO in the browser and OTP on mobile, for instance — but employees will experience them as separate sign-in journeys.
Everything sits in one Authentication setup section. Save is in the page header and becomes available once you change something; Remove authentication is in the ⋮ menu beside it.
Authentication method
Choose a Select authentication method. The rest of the section changes to match.
| Method | When to use it |
|---|---|
| OTP | A one-time code sent to the employee's email or mobile. No identity provider needed. This is the default |
| SSO | SAML-based single sign-on against your identity provider |
| OAuth | OAuth sign-in with Azure or Google |
There's no Custom method for the apps.
Settings shared by every method
Add allowed domains tells the apps which bot to send a work email address to. Enter the domain part of an email address, such as abc.in, and press Enter. It routes rather than restricts: employees on other domains can still sign in if they already have a record on this bot, and who gets in is decided by the bot's access rules on Web authentication and Other auth settings. A domain can belong to only one bot, so saving one that another bot already holds is refused. The field is optional, but if your organisation has more than one bot it decides where employees land — see How the mobile and desktop apps choose a bot at sign-in.
Allow login via mobile number lets employees enter their phone number to receive a one-time code, which often suits a mobile-first deployment better than email. It only works for employees who have a mobile number on their profile.
Send test OTP to email verifies delivery without leaving the page. Enter an address and click Send test OTP; the button stays unavailable until the entry is a valid email. Once mobile login is on, Send test OTP to mobile appears as well.
SSO
Choose a Select SSO type:
| Type | What it does |
|---|---|
| Single IDP SSO | One SAML app for everyone. Pick it under Select SAML app. This is the default |
| Multiple IDP SSO | Several SAML apps, each serving the employees on its own email domains |
The SAML app dropdown lists Live apps only. Create SAML app at the top of the dropdown opens the SAML app creator in a new tab. SAML apps themselves are managed on SAML apps.
With multiple IDPs, each row takes a SAML app and its Allowed domains for SAML app. Use Add more for further providers. Every row needs a SAML app, and either every app has its own domains, or exactly one app has none and is marked Set this app as default to catch everyone else.
Profile and field mapping
| Setting | What it does |
|---|---|
| Save SAML profile | Stores selected SAML attributes, such as department or location, on the employee's profile at each login. Turning it on reveals Add SAML profile fields, which is then required |
| Create integrations user | Available once Save SAML profile is on. Also creates the integrations user after a successful SSO login, mapping each SAML profile field to an Integration profile field |
| Login field mappers | Uses a SAML attribute other than email to identify the employee. Each row maps an Auth field to a Profile field |
| Successful login message | What employees see once they're signed in. Up to 200 characters |
If the identity returned at login doesn't resolve to an employee, sign-in succeeds but the assistant can't personalise anything or act on that person's behalf.
OAuth
Pick an OAuth provider — Azure or Google. The page won't save without one.
Passcode and biometrics
These two options are specific to the installed apps and have no equivalent in the browser.

Apps authentication with passcode, biometrics and inactivity timeout
| Setting | What it does |
|---|---|
| Enable passcode | Lets employees set a PIN so they can get back in without waiting for an OTP each time. They create it on their first login after you enable it |
| Enable biometrics | Appears once passcode is on. Lets employees use fingerprint or face recognition instead of their passcode, on devices that support it |
Treat the passcode as the foundation and biometrics as the convenience layer on top — a device that can't do biometrics still has the passcode.
Inactivity timeout
Enable inactivity timeout signs employees out after a period of inactivity. Turning it on reveals Inactivity duration — default 30 minutes, maximum 30 days.
This is worth more thought here than in the browser. A phone stays signed in in someone's pocket for weeks, so the tolerance for a long idle session is lower than on a managed desktop.
Token refresh, session duration and IP restrictions are browser-only and are set on Web authentication.
Behind the scenes
In a browser or in Teams, the link identifies the bot. The apps only get an email address or phone number, so Leena AI first works out which bot the person belongs to — by email domain, then by their existing employee record — and then applies that bot's access rules and sign-in method. For the full sequence, and how to set up a UAT bot and a production bot so employees land on the right one, see How the mobile and desktop apps choose a bot at sign-in.
Saving and removing
Save applies the configuration, and a confirmation appears. If anything is invalid, the affected fields are highlighted and nothing is saved.
Remove authentication, in the ⋮ menu, clears the setup entirely after a confirmation prompt. Employees can't sign in to the apps until a new authentication method is configured.
Updated 15 days ago
