Mobile deployment

Rolling the field application out to teams has three parts: the organisation has to be enabled, the application has to reach the team's phones, and each phone has to be registered. This page covers what Virtik does for the first and third, and is plain about the second.

1. Enabling the organisation#

Mobile access is part of the organisation's plan and has to be enabled for it. In an organisation where it is not enabled, signing in to the mobile application shows "Mobile access isn't available yet" and tells the person to contact their administrator or Virtik account team. Nothing else in the application is reachable.

An administrator sees the status in the web application, under Admin → Platform, on the Mobile Operations page. It has several tabs: Overview shows whether mobile access is enabled, Access & Roles holds the policy settings, and Devices lists the devices.

2. Getting the application to devices#

There is no public download, so there is no link here. See Downloads for the current position. Distribution of a build is arranged with your team during onboarding, which also covers device enrolment and the permissions the application needs.

The application asks the device for permission to use the camera, microphone and photo library, and for location while the application is in use. Where the organisation's Location Capture policy is on, the application asks for the "always" location permission itself, which the person has to grant.

3. Registering and revoking devices#

Devices are registered automatically, for an organisation that has mobile access enabled and not from a browser. The first time a person signs in to an organisation on a device, that device is recorded as active; later sign-ins update when it was last seen. There is no pairing code and no approval step.

An organisation administrator can see the list of devices on the Devices tab, and can revoke one by giving a reason. A person can also revoke their own device. A revoked device is signed out the next time the application checks, and a revoked registration is not reactivated.

The Access & Roles tab has three policy settings for the organisation: Offline Mode, Location Capture and Push Notifications. Each is Disabled, Test or Live, and the default is Disabled; non-administrators see them read-only. Push notifications are not delivered in this release.

What remains with Virtik#