Bring Your Own Device
By DBLogic on 27/02/2018

When you’re planning your tailor made software, it’s worth thinking about how you will manage the challenges of BYOD (Bring Your Own Device). What is your policy for employees that want to connect their own devices to your systems? With the capabilities of today’s handheld devices it’s no longer just a case of making sure your emails are accessible and secure. Additionally, what are you going to do if an employee wants to use their work laptop at home?

The initial reaction is often to implement a blanket policy that does not allow any connections from hardware that you haven’t supplied. While it’s a straightforward approach, there are a couple of problems.

The first is when you receive a request from someone to use their own device because it already has the adaptive technology installed on it that they require to work efficiently. This can include colour overlays, text readers, magnifiers and speech to text software etc. Your choice is to either set up one of your own computers with all the required adaptations, or allow the individual to use their own hardware. People often have a range of technological adaptations that they have spent time integrating and adjusting so that it suits their specific requirements. Trying to duplicate the set up on a different device will be time consuming.

The second is that you will have to supply laptops/desktops/tablets/smartphones for everybody and if people want to work away from your office they will have to take the hardware with them. It can get expensive providing multiple devices to employees. Also, having your own devices out “in the wild” can present its own crop of security concerns.

It’s good practice, with any system, to have your data compartmentalised so that your employees only see the information that they need to do their jobs. Not everyone needs to know your clients’ addresses and bank account details! Setting out a secure structure when your system is designed makes managing BYOD and similar issues far easier.

As an example, you might decide that only people with accounts functions need to see clients’ bank account details. You could add a further condition that the user’s device needs to be connected to the work’s intranet before the information is made available. Obviously, observing best practice with passwords and security is a must as well. By thinking through how people will want to work and what information they actually need to access you can ensure you’re providing a secure environment for your data.

If you’d like to talk about BYOD and how your software could be designed to take advantage of it, then give us a call.