Other auth settings
Other auth settings holds the access controls and authorization rules that sit around sign-in — who may sign in at all, and whether an authenticated person is actually allowed through.
Sign-in itself is configured elsewhere: Web authentication for browsers, Apps authentication for the mobile and desktop apps.

Where to find it
Open the Admin Console, then go to Leena Channels → Other auth settings.
The page has two sections, Access & security controls and Channel authorization expression. Save is in the page header and becomes available once you change something.
Access & security controls
Five switches, each off until you turn it on.
| Setting | What it does |
|---|---|
| White-label this assistant | Removes Leena AI branding from login pages and the system emails employees receive |
| Restrict login to directory users | Only people synced from a connected directory, such as Active Directory or Workday, can sign in. Everyone else is blocked |
| Block personal email addresses | Stops anyone using a personal email provider, such as Gmail or Yahoo, from signing in. Only work addresses are allowed |
| Route personal emails via SSO | Employees with personal email addresses sign in through your configured method, such as SSO, instead of getting an OTP on mobile and desktop |
| Allow OTP login for unregistered email addresses | For SSO and OAuth bots with Restrict login to directory users on. Employees whose email domain isn't one of your registered SSO domains get an OTP instead of being denied, and aren't removed during sync. They must still exist in your synced HRMS data |
Two of these also appear in Employee SyncBot users → User Sync → Sync setup → Authorize users shows Restrict login to directory users and Block personal email addresses read-only, labelled there as Only authorize synced users and Block login from personal email domains. They're the same settings, and this page is where you change them.
Channel authorization expression
Rules an authenticated employee must satisfy before they're let through, built without code.
Rules are built as groups. Conditions inside a group are joined with And — add one with And condition. Groups are joined with Or — add one with Or group. Each condition is a Key (an employee attribute, such as role), a Condition, and a Value (such as sales), and all three are required.
Available conditions: is equal to, is not equal to, equals (ignore case), is any of, is none of, contains, does not contain, starts with, ends with. "Is any of" and "Is none of" accept several values.
Use And inside a group to require every condition — the stricter and more common choice. Use separate Or groups where any one of several sets of conditions is enough, such as accepting people from either of two departments.
With no rules at all, access falls back to the allowed domains on Web authentication.
The same rules appear in Employee SyncThese are the rules shown as Employee authorization rules under Bot users → User Sync → Sync setup → Authorize users. Editing them in either place changes both.
They're separate from the JavaScript Channel authorization expression on Web authentication, which is stored on its own.
This gates access for everyone on the channelRules that no one satisfies lock all employees out, even though their sign-in succeeds — and the symptom looks like an authentication failure rather than an authorization rule, which makes it slow to diagnose.
Test with a real account before saving, and keep the rules as simple as the policy allows.
Saving
Save applies the configuration. A confirmation appears on success, and an error if the configuration couldn't be saved. If the page can't load the current settings, it shows an error instead of the form and Save stays unavailable, so nothing gets overwritten with blanks.
Updated about 1 month ago
