Mobile app pages: enabling them for your company

Added · Updated

The mobile app does not show everything that exists in the system. You choose which of the pages available in the mobile app your employees see on their phones — one switch per page, on one tab. This is also the screen to visit when somebody says "you enabled it and I still see nothing in the app": the switch is only one of four conditions, and the other three are settled elsewhere.

Animated overview: the route to the Mobile app tab, enabling a page and saving, badges and locked rows, the four visibility conditions and the edge cases — steps 1 to 5
The whole process in one place (it loops). Each step below explains one part.

1. Opening the Mobile app tab

The route to the setting: Administration then Company in the left menu, then the Mobile app tab in the tab strip, and the Pages in the mobile app heading with its explanation
① Admin → Company · ② the Mobile app tab · ③ the Pages in the mobile app heading.
  1. In the left menu open the ADM tab (if the tab strip is shown), then Admin and inside it Company.
  2. In the company settings tab strip pick Mobile app — the last tab, with a phone icon.
  3. Access requires company administrator rights. An employee without that right doesn't even see the Company item in the menu.
  4. The heading states what this tab does: you choose which of the pages available in the mobile app your employees see on their phones. The list is shorter than the list of pages in the system — see step 4.
  5. The blue note under the heading is a reminder of what gets forgotten most: user permissions still apply alongside this setting. An employee sees a page only if they have the right to access it.

2. Enabling and disabling a page

The card listing the pages: a counter of enabled pages, an unsaved-changes badge, a switch and state per row, the bottom bar with Discard and Save, and the confirmation after saving
① a switch per page · ② the enabled counter · ③ the unsaved-changes badge · ④ Save · ⑤ Discard.
  1. Each page is one row with a switch on the right. Next to the switch the state is spelled out — Enabled or Disabled — so you never have to infer it from the knob position.
  2. Tap the switch to change the state. Under the page name sits a short description of what the employee gets on the phone, e.g. "Clocking in and out through the phone as a kiosk device".
  3. At the top of the card is a counter: X of Y pages enabled for your company. Use it as a check — if the number isn't what you expect, somebody has been changing things.
  4. While you have unsaved edits, an N unsaved changes badge appears on top of the card and the edited rows are lightly marked. The bar at the bottom of the screen carries the same count.
  5. Click Save. The button is inactive while there is nothing to save, so you cannot "save" without a change. The confirmation reads Mobile page settings have been saved.
  6. A switch on its own changes nothing for employees — until you save, the change exists only on your screen.
  7. If you got it wrong, Discard returns every switch to the last saved state. The button only appears when there is something to discard.
  8. The setting applies to every employee in your company, as the save bar says. There is no per-person or per-department enabling — that is what access rights are for.

3. Badges and locked rows

The badges next to a page name and what they mean, and the two reasons a row is locked: the page is not enabled for the company in the system, or it is excluded by the package
① badges: Mobile only · Web + mobile · min. version · Unavailable · ② two reasons for a locked row.
  1. Mobile only means the screen exists only in the app and has no web counterpart — this is where it is enabled for the first time.
  2. Web + mobile means the same screen also exists on the web; here you decide only about its phone version. Switching it off here does not touch the web version.
  3. min. v1.1.0 (or another version) means the page needs a newer app version. On an older one the item won't appear even when enabled — see step 5.
  4. Unavailable with a padlock means the row is locked and the switch cannot be tapped. The full reason is written under the name, and a short version sits in the padlock tooltip.
  5. The first reason: the page is not enabled for your company in the system, so it cannot be enabled on mobile either. The second: the page is switched off by the package your company uses.
  6. Both reasons come from the web side, not from mobile, and are not settled on this tab — that is a conversation with InSync365 support.
  7. When at least one row is locked, the badge on top of the card reads N unavailable instead of Mobile app, so you don't have to scroll to notice that something is blocked.

4. When an employee actually sees a page

The dialog with four conditions: the page exists in the mobile app, it is enabled for the company, the employee has the access right, and the app is recent enough; one failing condition hides the item
① clicking i opens the four-condition dialog · ② one failing condition hides the item.
  1. Next to the name of some pages sits a small "i" icon. Clicking it opens the When an employee sees a page on the phone dialog.
  2. Condition 1 — the page exists in the mobile app. InSync365 support decides this at system level; that is why only some pages appear on the tab, not every page in the system.
  3. Condition 2 — it is enabled for your company. That is the switch from step 2, the only condition you control from this screen.
  4. Condition 3 — the employee has the access right to that page. Rights are edited under Administration → Access rights. An enabled page without the right does not appear.
  5. Condition 4 — the app on the phone is recent enough. A page with a minimum-version badge will not appear on an older app even when enabled.
  6. All four have to hold. When somebody reports they can't see an item, in practice it is usually condition 3 or 4 — an access right, or an old app version. Check those before touching the switch.
  7. For the menu list in the app to change, the user usually needs to reopen the app. If an access right was just granted, signing out and back in is the safer route.

5. Edge cases

Four edge cases: the warning for a screen not in the app yet, the empty screen with nothing to configure, the discard-changes dialog and the message about a change rejected on save
① a screen not in the app yet · ② nothing to configure · ③ leaving with unsaved changes · ④ a change rejected on save.
  1. If you enable a page that does not exist in the app yet, an amber warning naming that page appears under the card. You can leave the setting on — it will take effect by itself once employees install a newer version.
  2. If the card is entirely empty and reads No pages to configure, no page is currently available in the mobile app. That is not a setting you can change — contact support. In that state there is no save bar either.
  3. If you try to leave the tab with unsaved edits, you get a Discard changes? question with two options: Stay on the page or Discard changes. Edits are never lost silently.
  4. The message Some changes were not saved because the page has been switched off on the web means somebody else switched that page off for the company meanwhile. The other changes were saved normally and the list was refreshed — that row will now read Unavailable.
  5. If an error appears while saving, press Save again. The switches stay as you left them, so you don't have to walk the whole list again.

6. Checking the result for one employee

  1. Scroll below the card of switches. The second section of the same tab is What the employee sees in the mobile menu.
  2. Pick a person in the Employee field and you get the exact list of items they receive on their phone — same icons, same order, numbered so you can compare line by line.
  3. The counter reads X of Y enabled items: Y is what you enabled here, X is what that person reaches. A gap between the two is what their access rights removed.
  4. Use it right after saving, on one or two employees, to confirm the change landed where you expected. The section is read-only and changes nothing.
  5. Full walkthrough: Checking what an employee sees in the mobile menu.
This tab decides only what is available on the phone — it does not change the web app and it does not grant rights. If the screen still shows a notice that settings are "stored but not applied yet", that note is left over from an earlier version; the setting does apply.

Related: Checking what an employee sees in the mobile menu · Roles · The mobile kiosk: clocking in from a phone · Company notifications · Creating a user account