The screen in the window has been showing the same three slides since a promotion that ended two summers ago. Nobody in the business can say with confidence who put them there or who can change them. The kiosk in reception has been sitting on the same desktop login since it was installed, and a customer found the corner of the screen that closes the app.
Neither was a bad decision. Neither was an IT decision.
That distinction matters. Digital signage, menu boards, queue displays, self-service kiosks, visitor sign-in tablets, warehouse and despatch screens, and window displays are often treated as fixtures or specialist equipment. In practice, each is a small computer with an operating system, storage, a network connection, a login, an app and often a licence.
And it is almost certainly missing from the asset register, patch cycle and leaver checklist. It may also be the only computer in the building that customers touch.
The estate nobody counted
Start with a walk round the business. There may be a display behind the shop window, menu boards above the counter and a queue-number screen in a waiting room. Reception may have a self-service kiosk or a tablet on a stand where the paper signing-in book used to live.
Go further. A warehouse may have pick-and-pack screens at workstations and a despatch display near the loading bay. There may be a training-room panel, a digital noticeboard in a branch, or another screen in reception. Some displays are obvious. Others are a small player tucked behind a panel, quietly connected to the network and playing content from somewhere else.
Count the devices, not just the screens. A panel may rely on a separate media player, computer or tablet. A single display can therefore represent more than one device to manage. Add up the screens, players, tablets, peripherals, apps and content accounts, and the estate often looks quite different from the one on the IT inventory.
The point is not that every display is a serious security problem. It is that a business cannot assess or support devices it does not know it has.
How they all arrived without anyone deciding
A marketing manager bought a screen for a campaign. An installer fitted a player behind the panel and left an administrator password. A tablet was mounted on a stand because the paper sign-in book kept going missing. A warehouse team added a display because it made orders easier to follow.
Each decision made sense in its setting. The trouble begins later, when the original project is over and the device remains. The supplier may have created the account, the marketing manager may have uploaded the first content, and a member of the operations team may know how to restart the player. None of those people necessarily owns the device end to end.
This is how a business acquires networked computers without recognising them as part of its IT estate. The agency changes, the staff member leaves, the supplier contract expires, or the branch is refitted. The display stays. The login and the support assumptions stay with it.
Suppliers are part of the picture, too. A business may depend on an installer, content agency, hosting provider or specialist maintenance firm without having a clear record of who can access what. The NCSC supply-chain security guidance offers a useful framework for thinking about supplier oversight. A supplier can be trusted and still need defined access, responsibilities and an orderly exit.
The three things every screen holds
The first thing is a content account. Whoever holds that login may be able to publish to one display or to every screen in the estate at once. On a public screen, publishing is the business speaking in public. If a former marketing assistant still has the password, they may still have a voice in the shop window.
That makes the content account a security question, not merely a design detail. It may be forgotten because it is managed in a content portal rather than on a familiar company computer. Yet an old account could publish an incorrect price, an expired promotion, an unsuitable message or content intended for an internal audience. If several people share one login, the business may not be able to identify who changed what or remove access for one person without disrupting everyone else.
The second thing is a device account. It may be a shared local administrator, a password that has never been changed from its default, or a service account connected to the wider network. Sometimes a player has been joined to a company domain for convenience, and nobody can say who owns the account or what access it needs.
The third is personal data, where the screen or the service behind it collects or displays information about people. A sign-in tablet may record visitor names and arrival times. A queue system might connect a ticket to a name or appointment. An internal message or staff rota may appear on a display that is visible to visitors.
These are different exposures, but they share one basic requirement: someone needs to know which accounts exist, who controls them and what information flows through them. The content login deserves particular attention because it can be overlooked by teams that understand device security but assume publishing access is harmless.
The physical exposure
A public-facing device is different from a computer behind a locked office door. A USB port may sit at child height on a kiosk. A keyboard shortcut might drop a supposedly locked-down application back to a desktop. A browser running behind the app could be pointed elsewhere. An on-screen keyboard might reveal recent searches, while a tablet with no passcode could expose whatever was left open.
Sometimes the exposure is less dramatic. An activation prompt, update dialogue or error message can appear to customers on a busy Saturday. A kiosk may be usable for its intended purpose, yet have an obvious route back to the operating system. The fact that a device has a full-screen app does not, by itself, mean that the rest of the device is secured.
The NCSC’s guidance on managing deployed devices makes the neutral point that devices still need to be maintained once they are out in the world. A screen installed in a shop, branch or warehouse is no exception. The broader NCSC device security guidance provides context for choosing, configuring and managing different types of device.
For Windows devices, Assigned Access and Microsoft’s kiosk configuration guidance illustrate what a restricted single-app profile can do. It can run a chosen app full-screen and limit what else a user can open. The comparable Android dedicated-device guidance describes kiosk-style devices configured for a limited purpose.
These are neutral examples of how a managed device profile can limit the experience to what the device needs: one app, no taskbar or general-purpose browser, no removable media, and fewer routes to escape to the desktop. They are not a reason to assume that every screen needs the same configuration. The right profile depends on the device’s job, operating system and support model.
Who is allowed to say what, on which screen
Publishing to a public display should be a permissioned role, not a shared password passed around because it is quicker. A short written rule can define which screens exist, who may publish to each, and what approval a price or service claim needs. It should also state what must come down and when.
Content needs an owner and a review date, just as a contract does. Stale content is a live commercial error, not a cosmetic one. An expired offer can create confusion at the counter; an outdated service notice can send a customer to the wrong place. In some sectors, a stale notice may carry a compliance consequence, so content should be treated with the care its purpose demands.
Readability is part of this responsibility. Can someone read the screen from where they will actually be standing? Is the contrast clear? Is the font large enough, does each slide stay up long enough, and can the display be read from three metres away in poor light? A beautiful slide that cannot be read is a decorative asset with excellent lighting.
The GOV.UK accessibility guidance for public sector websites and apps and the service manual introduction to accessible services provide useful principles for making content clear to the people using a service. The public sector guidance concerns public sector bodies. It is not a claim that the public sector accessibility regulations apply to every private business. Clear, readable information remains a sensible design choice for any organisation serving people.
Personal data on a public screen
A visitor sign-in tablet may store names and arrival times. A queue display might show someone’s name alongside an appointment. A screen that once carried a staff rota or internal message may reveal information to visitors simply because its location changed or its content was never reviewed.
The practical questions are straightforward. What is collected, why is it collected, how long is it kept, and who can read it? The ICO’s guidance on the right to be informed explains the importance of telling people how their information is used. Its guide to lawful basis explains that an organisation needs to identify and document a valid basis for handling personal information.
For a sign-in tablet, this means considering what information is genuinely needed for the purpose, where privacy information is shown and what the retention arrangements are. It also means checking who can retrieve the records and whether they remain on the tablet after use. A paper book can be left open on a desk; a digital version can be left accessible in a browser or account. Neither is automatically private because it is convenient.
Some devices may also capture images. If a device uses a camera or another image-capture feature, consider whether the use creates a need for a data protection impact assessment. The ICO’s DPIA guidance explains how to assess the risks of processing that may be likely to result in high risk. The ICO’s data security guidance also sets out the principle of using appropriate security measures for the risks involved.
What actually goes wrong
A panel reboots into a desktop during trading hours. A kiosk freezes on an update screen while a queue forms in front of it. A content account remains shared with an agency after the contract ends, because nobody knows who should remove the access.
A shop-floor display sits on the same flat network as the till system and file server. A pick screen keeps running an operating system the supplier stopped supporting years ago. A visitor tablet has no passcode and a browser history full of the last person’s searches. None requires an elaborate chain of events. Each begins with a device that was treated as a screen rather than as a computer.
Other failures are quieter. A queue display is fed from a mailbox belonging to someone who left. A player still uses its default password and can be reached from the internet. A public screen displays an internal notification because a phone paired with it belonged to an employee using a personal handset.

None of these problems is dramatic on its own. That is why they survive. Each one has a workaround, and the workaround is often a person rather than a process. Someone knows how to close the dialogue, restart the tablet, call the old agency or walk over to the display and unplug it. That person may be on holiday, may have left, or may simply have another job to do.
A fault, a leaver or a lost tablet needs a documented route rather than an informal favour. Helpdesk Support can provide an operational route for reporting faults and changes, with an agreed way to escalate access concerns, leavers and missing devices. If the screen has a separate supplier or content account, the support process should include that dependency rather than stopping at the edge of the office network.
Bring the screens under management

Start with an inventory that is useful when something fails or changes. Record the location, what each device runs, what it displays, who publishes to it, which account it uses, how it reaches the network, who supports it, when its warranty ends and when it is due for replacement. Include the player behind the panel, not just the panel itself.
Then decide how devices should connect. A public-facing kiosk should not be able to reach a till, server or finance system simply because the network was easier to configure as one flat space. Separation limits what a compromised or misconfigured device can communicate with. A review of Network Solutions should therefore consider the purpose of each screen, the services it needs to reach and what should remain out of reach.
Build standard device profiles for screens that do the same job. A menu display and a visitor tablet may need different settings, but identical devices should not each be improvised. Set up the required app, user access, update behaviour and permitted connections, then apply the profile consistently. Remote management and reboots scheduled outside opening hours can avoid a drive to a branch just to power-cycle a panel.
Patching belongs on the same discipline as the rest of the fleet. Devices that cannot receive updates or be managed need an explicit decision, not indefinite acceptance by default. The NCSC 10 Steps to Cyber Security and its Cyber Essentials overview offer broader context for common security controls. They do not make kiosk hardening a standalone legal requirement; they help frame a proportionate approach to device management and security.
Publishing access should be assigned as a role, with individual accounts where the service allows it, rather than a password passed between staff and suppliers. When someone leaves or an agency contract ends, access should be reviewed and removed through the same joiner, mover and leaver process used elsewhere in the business. Managed IT Services and Cloud Solutions can be bolt-on execution services to carry out an agreed management approach, not replacements for deciding what the business needs.
Where a despatch or shop-floor screen reads from an IBM i system, give it an account with only the rights the display requires. A shared operator profile may be convenient, but it can give the screen more reach than its function warrants. That is a specialist IBM i Management consideration. If a queue or customer-notification screen is fed from Business Central or a service module, scope the data flow as part of a governed implementation, such as a Dynamics 365 Jump Start, rather than letting whoever needs the screen wire it up informally.
Where content is published to the screens from a hosted platform, the accounts, storage and update arrangements behind that service belong in the same review as the devices themselves. Cloud Solutions covers that side of the estate, and a screen is only as current as the platform feeding it.
The cost side
Panels fail and players stop receiving updates. Replacement is better treated as a decision with a date than an accident during trading. A replacement date gives the business a chance to review whether the device still serves a purpose, whether it can be supported and whether its software or content arrangements still make sense.
Signage contracts can bundle connectivity, content subscriptions and support. Displays in closed or refitted branches may keep attracting charges for all three because the accounts and invoices are held in different places. Reconcile the contracts against the inventory, then confirm what is still used, who owns the agreement and when it can be reviewed. Technology Expense Management can support that reconciliation, but an inventory review is not a promise of savings. It is a way to see what the business pays for and decide whether it remains justified.
The same estate may increasingly carry announcements, out-of-hours messages and queue systems, linking displays with Voice and Connectivity. That connection should be understood when planning support, updates and renewal dates. If the display, its connectivity and the service feeding it are billed separately, the business needs a joined-up view of those dependencies.
Screens in a bad week
A screen that shows opening hours or a queue number is part of the customer-facing service. It belongs in the continuity plan. Decide what the screens should show during a site outage, who can change content from outside the building and what happens if the content platform itself is unreachable.
The answer may vary by screen. A blank panel in a waiting room is an inconvenience. A display still announcing normal opening hours during a closure is a genuine problem. A warehouse screen that cannot show despatch information may affect operations even when the rest of the building is working.
The same message may need to reach people who ring the office rather than walk past it, which makes customer messaging a Voice and Connectivity question as much as a signage one.
The plan should identify a safe fallback, the person authorised to publish it and the route for getting access if the usual platform fails. Disaster Recovery should account for the practical restoration of customer-facing devices and their content, not only servers and business applications. The recovery approach should be realistic enough to use when the person who normally manages the screen is not available.
A first-month tidy
A first-month review does not need to turn into a major technology programme. It needs to replace guesswork with a view of the devices, their accounts, their content and their support arrangements.
-
List every panel, player, kiosk and tablet by checking invoices and supplier accounts, then walk round the building. Do not rely on memory or on an asset register that was created before the screens arrived.
-
Record the account behind each device and who can currently publish to it. Include supplier and agency access, as well as the staff who use the content service.
-
Change credentials that are still default or shared administrator passwords. Give access to named people where possible, and remove accounts that no longer have a clear purpose.
-
Put public devices on a separated network segment. Confirm that each device can reach the services it needs without having a route to business-critical systems it does not need.
-
Build one standard profile and apply it to every identical device. Confirm that it launches the right app, limits unnecessary access and can be updated and supported.
-
Write the publishing rule and name an owner for each screen. Include who approves prices, service claims and other sensitive material, and who removes content when its purpose ends.
-
Give content a review date so stale material has somewhere to go. This applies to a promotion as much as to opening hours, internal notices or service information.
-
Add the whole set to the asset register with a replacement date and review it alongside the bill. Where no one in the business has time to maintain the inventory, device profiles and recurring review, Managed IT Services can provide that operational support under an agreed strategy. Fault reporting and access changes should also have a known route through Helpdesk Support.

The screen is a computer
These devices are a small, visible example of a wider question: is anyone in the business accountable for the technology that quietly joined the estate? The answer needs to cover more than installation. It should include the business purpose, ownership, access, network design, content approval, support, cost and replacement.
A consultancy-first approach puts those decisions before the delivery work. A Fractal IT Director can provide the strategy layer, aligning the technology with business priorities and defining what needs to happen next. Specialist channel partners can then add the expertise and capacity needed to carry out the plan.
Cloud Solutions, Managed IT Services, Network Solutions, Helpdesk Support, Disaster Recovery, Technology Expense Management and Voice and Connectivity are bolt-on execution services that carry out the decision. They are not substitutes for deciding what the organisation needs, or for assigning someone responsibility for the devices and services that deliver it. The wider Evestaff group can be reached through evestaff.co.uk.
A screen on a wall looks like furniture, but it is a computer with a password, and it should be treated like one.
SEO keywords:
Cloud Solutions, Disaster Recovery, Dynamics 365 Jump Start, Helpdesk Support, IBM i Management, Managed IT Services, Network Solutions, Technology Expense Management, Voice and Connectivity, IT Consultancy, Fractal IT Director, digital signage management, kiosk security, public-facing device security, signage content ownership, display screen estate
Join The Discussion