Colour theme
Book a consultation

Ten checks for mobile apps used at work

Review mobile app sources, permissions, sign-in, updates and work-data handling, with clear steps for suspicious requests and lost phones.

An illustration of a smartphone displaying a shield and a security switch.

A phone used for work may hold email, client documents, approval requests and sign-in tools. Each app adds another decision about access and where business information goes.

Use these checks when installing an app or reviewing one already in use. Follow your employer’s rules on which phones can be used for work. For personal phones, the BYOD guide covers the separate questions of ownership, enrolment and privacy.

1. Install the right app from the right place

Use your organization’s app catalogue or the official store listing identified by IT. Check the publisher and product name, especially when several apps have similar icons.

Don’t install an app, configuration profile or certificate from an unexpected text message or support call. A store listing tells you where to get the app. Whether it should handle your business’s information is a separate check for IT.

2. Treat reviews as one input

Ratings may describe usability, advertising or subscription problems. They won’t tell you how the app protects data or who can access it.

For a new business use, ask IT to check the provider, account type, terms and data handling. Tell them the task you need to complete as well as the product you’d like to install.

3. Match permissions to the task

Review access to location, contacts, photos, camera and microphone. A receipt app may need a selected image without needing your whole photo library.

Apple’s permission guidance and Google’s Android instructions explain how to review and change access. Options vary by platform and version. If a necessary task stops working after a change, ask IT to look at it. Don’t just switch on every permission.

Permission settings don’t describe every upload you make or every action available through a connected business account. Review those separately.

4. Keep the phone supported and updated

Check that the operating system still receives the updates your organization requires. Install the updates your organization requires and restart when prompted.

Tell IT if updates repeatedly fail, storage is insufficient or the device no longer meets work-access requirements. Don’t bypass management controls to keep an old app running.

5. Use the right business account

Sign in with your work account where the app supports it. Avoid placing client work in an app tied only to a personal email address.

For a separate password, use the password manager your business has chosen and a unique password. Don’t share a login between staff to avoid adding another user. The shared-login guide explains the ownership and recovery problems that creates.

6. Complete the supported sign-in protections

Use the MFA or passkey method required for the service, with a recovery route the business can support. Never approve a sign-in request you didn’t initiate.

Report repeated or unfamiliar requests. An extra sign-in step helps protect access. It won’t stop a malicious app, so still check what the app is connected to.

7. Connect the way IT has set up

Use the connection method required for the information and application. Don’t bypass certificate warnings or install a profile offered by a public hotspot to fix access.

Some systems may need the company VPN. It can’t tell you whether an app or sign-in page is legitimate. If the connection is uncertain, stop the sensitive task and check with IT.

8. Protect the unlocked session

Use a strong device passcode, automatic locking and any required app lock. Keep sensitive notification previews off a screen others can see.

Signing out can be useful on a shared device, but it may leave downloaded files behind. Use a shared phone for work only when IT has checked and agreed to the setup.

9. Keep apps and built-in protections current

Install app updates and report warnings. On supported Android devices, Google Play Protect checks apps for harmful behaviour and can warn, disable or remove them. Don’t turn it off to install something a message recommends.

IT should confirm the protection and management available on each platform. A clean scan can still miss harmful behaviour.

10. Know how to report loss and remove access

Keep a reporting contact available without the phone. Tell IT promptly about a missing device, unexpected app or suspected disclosure, including which work accounts were in use.

Before removing a work app, confirm that required records are preserved. Uninstalling doesn’t necessarily close its service account, revoke a connector or delete the provider’s stored data. IT should check those steps and verify any requested removal of managed work information.

Contact us to review mobile work apps and make it easier for staff to get an app checked and supported.


Featured Image Credit