The Mobile app page in Settings decides which modules the Illizeo mobile app offers on phones, shows how many employees use it, and lets you block a person from using the app. This article describes this web setting. It is for administrators.
Before you start #
- The page requires “Settings — Access”, then the “Mobile app — modules and adoption” permission, in the “Platform administration” menu, “Global settings” section of the role matrix.
- The Access level lets you view adoption, module status, the list of employees and their sessions. The Execute level lets you open or close a module, block or unblock a person and sign out a session. Without it, the switches are greyed out and the buttons are not shown.
- By default, only the Administrator role holds this permission. Permissions are set in Settings › Manage Employees › Employee Roles (see Permissions & roles).
- A module can only be offered on phones if it is part of your subscription and installed (see Subscription & settings).
Opening the page #
Open Settings › Manage Illizeo › Mobile app. The Mobile app card has two tabs: Modules, open by default, and Employees.
Tracking adoption #
At the top of the Modules tab, the Who uses it block shows how many active employees have signed in from a phone at least once, out of all active employees, and the date of the Last activity on mobile.
Illizeo only records which app a session comes from since a given date. When older sessions exist, a sentence gives their number and the date the count starts from: the real number of users is then higher than the one shown.
Choosing the modules open on phones #
The Modules open on mobile block lists the modules the app can offer, each with a switch and its status, Visible or Hidden:
- Time tracking: clocking and the day view;
- Leave: balances and requests;
- Flex Office: the week and on-site check-in. This row only appears if the Flex Office module is enabled in your workspace.
- Flip the module’s switch.
- The setting is saved straight away and applies to all staff: closing a module hides its tab in the app; reopening it brings the tab back.
This setting can only close. A module that your subscription does not cover shows Not included in your subscription — the tab stays hidden whatever you set here. Its switch is greyed out: the module must first be subscribed and installed in your workspace.
Managing employees’ access #
The Employees tab lists every active employee, including those who have never signed in from a phone. Each row shows the name, email and status: the number of mobile sessions, Never seen on mobile or Blocked.
Blocking or unblocking a person #
- Find the person in the list.
- Click Block. Their open mobile sessions are closed and they can no longer use the app.
- To undo this, click Unblock.
You can block someone in advance, even before their first sign-in. Blocking only concerns the mobile app: the person keeps their access to Illizeo from a browser. It is not a security barrier: to actually close an account, deactivate it.
Viewing and closing a person’s sessions #
Click the chevron at the start of a row to expand their mobile sessions: Opened, Device, IP address and Last activity. The Sign out button closes a specific session, for example that of a lost phone; the person will have to sign in again on that device.
Last activity is updated every five minutes, not on every action. Sessions opened before Illizeo recorded the originating app do not appear in this detail.
Good to know #
- These settings trigger no email or notification: let your teams know if you close a module on phones.
- Closing a module on phones changes nothing about its use from a browser.
- To withdraw a module from certain people only, on every channel, set its access by person or by unit in the app store (see Subscription & settings).
FAQ #
Adoption shows zero although employees use the app. #
Sessions opened before the count started are not included. The sentence under the counter says when the count starts and how many older sessions exist.
I cannot flip a module’s switch. #
Either your role does not have the Execute level, or the module is not subscribed or not installed in your workspace.
