> [!WARNING]
> **Warning:** The Looker Mobile (Legacy) application will be deprecated on January 31, 2027. Use the [Looker application](https://docs.cloud.google.com/looker/docs/looker-core-mobile-app.md.txt) instead.

The Looker Mobile (Legacy) app lets users perform the following functions from a mobile device:

- [View their favorite and recently viewed content](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-navigating-to-content.md.txt#viewing_your_most_recently_viewed_or_favorite_content)
- [Access the boards that they follow](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-navigating-to-content.md.txt#navigating_to_content_from_boards)
- [Navigate to content in folders](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-navigating-to-content.md.txt#browsing_content_in_folders)
- [View Looks](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-viewing-looks.md.txt) and [dashboards](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-viewing-dashboards.md.txt)

Admins can enable the mobile app to let users [sign in](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-sign-in.md.txt) to their Looker instance on an Android or iOS device.


## Enabling the app for your instance

> When [IP allowlists](https://docs.cloud.google.com/looker/docs/2622/admin-panel-server-ip-allowlist.md.txt) are enabled, users cannot connect to the instance from their service providers' IP addresses.

Access to the mobile app is enabled for your instance by default. To disable or enable access to the mobile app for your instance, follow these steps:

1. Open the [**Settings** page](https://docs.cloud.google.com/looker/docs/2622/admin-panel-general-settings.md.txt) in the **General** section of the **Admin** panel.
2. In the **Feature Configuration** section of the **General Settings** page, choose **Enabled** or **Disabled** under **Mobile Application Access**.

   > [!NOTE]
   > **Note:** The **Mobile Application Access** setting applies to both the [Looker app](https://docs.cloud.google.com/looker/docs/looker-core-mobile-app.md.txt) and the [Looker (Legacy) app](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy.md.txt).

3. Select **Update** to apply your changes.

When the app is enabled for your instance, users can [install the app](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-installation.md.txt) and [sign in to your instance](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-sign-in.md.txt) on their mobile devices.

If you disable the **Mobile Application Access** setting for your instance, any existing mobile app sessions will be invalidated.

## Assigning mobile app access to specific users

Admins can use the [`mobile_app_access`](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-roles.md.txt#mobile_app_access) permission to grant specific users and groups access to the mobile app. To grant mobile app access to a specific user or group, follow these steps:

1. Ensure that mobile app access is [enabled for your Looker instance](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-enablement.md.txt#enabling_the_app_for_your_instance).
2. Assign that user or group a [role](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-roles.md.txt#assigning_roles) with a [permission set](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-roles.md.txt#permission_sets) that includes the [`mobile_app_access` permission](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-roles.md.txt#mobile_app_access).

Users with the `mobile_app_access` permission can [sign in to the mobile app](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-sign-in.md.txt) with email, a QR code, or biometrics. If a user does not have the `mobile_app_access` permission, Looker displays an error when that user tries to sign in to the app.

See the [Roles](https://docs.cloud.google.com/looker/docs/2622/admin-panel-users-roles.md.txt#assigning_roles) documentation page for information about assigning roles to users or groups.

## Forcing users to authenticate each time they log in to the mobile app

Admins can require users to sign back in to Looker every time they open the mobile app by enabling the **Force mobile authentication** setting in the [**General Settings**](https://docs.cloud.google.com/looker/docs/2622/admin-panel-general-settings.md.txt#force_mobile_authentication) section of the **Admin** panel. Enabling this feature also lets users [configure biometric sign-in](https://docs.cloud.google.com/looker/docs/2622/mobile-app-legacy-sign-in.md.txt#signing_in_with_biometrics). To enable this feature, follow these steps:

1. Navigate to the **Settings** page in the **General** section of the **Admin** panel.
2. Under **Force mobile authentication** , select **Enabled**.

When **Force mobile authentication** is enabled, users will be required to sign in to Looker every time they open the app on their mobile devices. Additionally, they will be logged out of the mobile app after 30 minutes of inactivity.

Users will also have the option to configure biometric verification. If users enable biometric verification, they will need to verify their identity using biometrics for each subsequent session, which will allow them to bypass other authentication methods such as email/password authentication or single sign on authentication.

## Considerations for customer-hosted instances

Admins of [customer-hosted](https://docs.cloud.google.com/looker/docs/2622/glossary.md.txt#customer-hosted) instances should consider the following requirements when enabling the mobile app for their instance:

- The web server and API endpoints must be publicly accessible or otherwise reachable by the mobile app.
  - To test connectivity, try accessing the URL of your Looker instance from a web browser on your mobile device.
- The [API Host URL](https://docs.cloud.google.com/looker/docs/2622/admin-panel-platform-api.md.txt#api_host_url) must have the same hostname as the instance URL and serve traffic on either port 443 or port 19999. The URL should follow this form: `https://<instance_name>.looker.com:<port>`

For additional information, see the [Looker API troubleshooting](https://docs.cloud.google.com/looker/docs/2622/api-troubleshooting.md.txt) documentation page.