Colour theme
Book a consultation

Setting rules for personal devices at work

Decide which work personal devices can access, explain employee privacy and management controls, and plan how to remove business data when access ends.

A woman using a smartphone at a desk with a laptop.

Someone adds work email to their own phone so they can answer a customer. Later, a colleague downloads client files to a home laptop. Both decisions affect where business information goes, even if no one has said personal devices are allowed for work.

Bring your own device (BYOD) can be workable for selected tasks. Decide what you’ll allow, what you can protect and what happens when access ends before staff start using it more widely.

Find out what staff already use

Ask which personal phones, tablets and computers access work accounts. Include contractors and temporary staff. Record the device type, its user, applications, information involved and who provides support.

Look beyond files deliberately saved to a folder. Email attachments, offline app data, browser downloads and personal cloud backups can hold business information too. Ask staff about those workflows without inspecting their private files or collecting personal passwords.

Then decide whether each workflow should continue, move into an app the business manages or move onto a company device. Give people a workable alternative while you change access rules.

Decide which work, on which devices

Reading a meeting invitation on a phone and exporting a customer database need different controls. Write down which tasks and information are allowed on each device type. Treat browser-only access as a workflow to assess; downloads and active sessions may still remain on the computer.

Use the Cyber Centre’s BYOD guidance to review technical risks and controls. Establish a minimum device standard: supported software, current updates, encryption, an automatic screen lock, the work apps you’ve chosen and MFA for work accounts. Restrict access from devices whose protections have been bypassed through rooting or jailbreaking.

Have your IT provider show how those requirements are checked and what happens when a device fails them. A written rule alone won’t configure an app or block an unsupported device.

For administrator access, sensitive records or extensive local file storage, consider a company device with controls suited to the role. Ownership alone doesn’t make it secure; it still needs configuration, updates and access management. Don’t allow a shared household computer if you can’t keep work access separate from other users.

Explain the privacy implications

The Canadian privacy commissioners’ BYOD guidance recommends assessing privacy risks and developing a clear policy with IT, HR, legal and other affected teams. It addresses both customer information and employees’ personal information.

Before enrolment, explain what the business and its provider can see, collect, change or remove. Include device details, compliance reports, location features if enabled, and the difference between removing work data and resetting the whole device. Choose controls that limit unnecessary access to personal information.

Have the policy reviewed for your province, sector and employment context. Employees acknowledging it doesn’t settle every question about lawful monitoring, access to private information or erasing a personal device. Provide a company-device option when the proposed arrangement isn’t suitable.

Test the limits of app management

Some systems protect supported work apps without managing the entire personal device. Others enrol a device or create a separate work profile. The controls differ by platform, application, licence and enrolment method. Ask for a demonstration using the devices your staff will use.

For example, Microsoft Intune’s selective wipe can remove company data from supported managed apps. Microsoft says the user must open the app for the wipe to occur. Until an offline phone reconnects and the app opens, assume the data is still there.

An app-management policy also can’t guarantee removal of every copy outside its control. Test what happens to attachments, downloaded files and contacts exported to other services. Record any remaining limitations and decide whether that workflow should be allowed.

Write a policy staff can use

Keep the operational instructions short enough to follow. Cover:

  • permitted devices, apps, tasks and information;
  • required security settings and how compliance is checked;
  • whether downloading, personal backups or device sharing is allowed;
  • what management can see and which removal actions the business can take;
  • who pays for mobile data, support, repairs and replacement;
  • whom to contact before repair, sale or replacement;
  • how to report a lost device and what happens at departure.

Test the arrangement with a small group before expanding it. Ask staff to complete real tasks and report problems. Include management licences, support time and training in the cost comparison with company equipment.

Plan for loss and departure

Give staff a reporting contact they can reach without the missing device. Your IT provider can block the device, revoke sessions and send a command to remove managed work data. A phone that stays offline won’t receive it, so record which actions completed and which are still pending. Use the business’s incident process to assess any exposed personal information.

For a planned departure, preserve required business records and coordinate account closure with removal of managed data. Some removal processes need an app to remain installed and able to communicate; confirm the sequence with your provider before deleting enrolment records.

Ask the employee to return or delete downloaded work files as the policy requires, and confirm it’s done before taking the device off your list of permitted devices. Disabling a cloud account doesn’t remove files already saved on the device.


Featured Image Credit