Shared Device and Kiosk Basics
This shared-device page gives employees a clear routine for checking the screen, signing in, completing one task, signing out, and reporting problems. Use it to reduce the risk of leaving another person’s session or information exposed.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Healthcare and clinics · Retail and customer service · Manufacturing and warehousing · Hospitality and facilities
Overview
Shared Device and Kiosk Basics is an employee-facing intranet page for people who use workplace devices in sequence. Its six-step routine starts by checking the screen, then covers approved sign-in, completing only the current task, signing out through the available controls, confirming the start screen has returned, and reporting a problem through the local route. A worked example shows how to respond when a kiosk is displaying another person's open session, while the contact section identifies the content owner and the support roles to confirm locally.
The supplied page is clearly labeled as a fictional Northstar Services example, dated 10 October 2026, and not live device or incident monitoring. Use it as a starting point for shared kiosks, common workstations, or other devices where a person must leave the session ready for the next user. Before publishing, replace the sample scope and scenario with confirmed local instructions, including the approved sign-in method and reporting route. The authorized device-specific reference section is a place to connect the relevant source; the template does not include a configured live reference or support integration.
This page is not a device-management procedure, security policy, incident-response plan, or substitute for privacy and security review. It does not establish controls for a specific system or guarantee regulatory compliance. Avoid using it unchanged where devices have different sign-out behavior, where local policy requires another response, or where a formal procedure is needed. Keep one authoritative home for detailed device instructions, and use this page to direct employees to that guidance and the correct local support role.
Standards & compliance context
- The sample routine encourages employees not to use another person's open session and to confirm sign-out, but it does not certify that a device or organization meets a privacy or security standard.
- Have the relevant privacy, security, or compliance owner confirm applicable obligations and local procedures before publishing the page as workplace guidance.
- Keep device-specific instructions and reporting routes aligned with the organization's authoritative policies; the template's reference section is not a verified policy link.
- Make the page accessible to its intended audience, including keyboard and screen-reader users, and apply WCAG 2.1 AA as an accessibility target for an audience-restricted intranet page.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Example scope and date
This notice marks the Northstar Services material as a dated fictional example, not live monitoring or guidance for another organization.
-
Fictional example: Northstar Services uses this page to describe a shared-device routine. This illustrative notice applies only to the sample setting and is dated 10 October 2026; it does not establish guidance for another organization or location. It is authored information, not live device or incident monitoring.
Use the device, then leave it ready for the next person
Follow this sequence from checking the opening screen through confirming sign-out and reporting an unresolved problem.
-
Follow your organization's approved sign-in method and any device-specific instructions. If the screen shows another person's information before you begin, do not continue in that session. Use the local reporting route described by your organization. Check the starting screen Confirm the device is at its sign-in or shared-use start screen. If another person's name, messages, records, or open work are visible, do not open or use them; report what you see through the approved local route. Sign in using the assigned method Use only the sign-in method your organization has approved for this device. Do not reuse another person's open session or share your sign-in details. Complete only your task Work in the application or service needed for your task. Before submitting or saving, check that the screen shows the right account or work context and that the information belongs to your task. Sign out when finished Use the application's sign-out control and, when provided, the device's shared-session sign-out control. Closing a window or walking away is not the same as confirming sign-out. Check the screen before leaving Wait for the sign-in or shared-use start screen. If your information remains visible or sign-out does not complete, stay with the device if practical and contact the designated support role. Report a problem through the local route Tell the designated device or workplace support role the device location, what you observed, and when it happened. Do not include another person's private information in an open message or photograph.
Worked example: a shared check-in kiosk
This scenario shows how to handle an already-open session without using or inspecting the previous user's work.
-
At Northstar Services, a fictional employee approaches a kiosk to complete a routine check-in. The kiosk is already showing a signed-in user's name and an open page. The employee does not inspect the page or try to finish the previous user's work. They step away from the screen and notify the locally designated device support role, describing the kiosk location and that another session remains open. Once the device is at its approved start screen, the employee signs in using the organization's assigned method, completes only the check-in task, signs out, and waits until the start screen returns. The useful distinction is simple: an open screen is not permission to use the prior session , and a closed window alone does not confirm that the shared session ended.
Authorized device-specific reference
Use this section for the confirmed source of instructions when a particular device requires more detail than the shared routine.
Who to contact
These owner and support roles clarify who maintains the page, handles device problems, and helps identify the local reporting route.
-
Content owner Workplace Experience For device faults, incomplete sign-out, or another user's information left on screen Device support role Local device or workplace support For help identifying the approved local reporting route Local supervisor or designated lead Local operations
How to use this template
- Confirm which shared devices and locations the page covers, then replace the fictional scope notice with the organization’s approved audience and instructions.
- Add the approved sign-in method, device-specific sign-out steps, authorized reference, and verified local reporting route without implying unsupported monitoring or integrations.
- Assign the page to its content owner and identify the local role responsible for device faults and incomplete sign-out.
- Publish the routine where employees can find it before using a shared device, and direct them to the approved reference when device instructions differ.
- Ask employees to follow the sequence for each session and report another user's information or a sign-out failure through the confirmed local route.
- Review the page when device behavior, approved instructions, support ownership, or the reporting route changes, and correct stale details promptly.
Best practices
- Name the devices and locations covered so employees can tell whether the routine applies to the screen in front of them.
- State the approved sign-in method using the wording employees see on that device, without including shared or personal credentials.
- Keep the distinction between closing a window and confirming sign-out explicit in both the steps and any device-specific guidance.
- Tell employees not to inspect or continue another person's open work, and give them a verified route for reporting it.
- Ask reporters to include the device location, observation, and time while excluding another person's private information from open messages or photographs.
- Link the authorized device-specific reference from its section only after confirming that the destination is correct and accessible to its intended audience.
- Assign a content owner and review the instructions when the device setup or local support route changes.
- Check the page on a mobile screen and use clear headings and readable contrast so employees can scan the routine at the point of use.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who is this shared-device page for?
It is for employees who use workplace kiosks or other devices shared between people. The example covers checking the screen, using the assigned sign-in method, completing only the task at hand, and confirming sign-out. Organizations should add their own device-specific instructions and local support route before publishing.
Does this page apply to every device or location?
No. The sample is fictional and explicitly limited to its illustrative setting; it does not establish rules for another organization, location, or device. Confirm which devices and work areas the routine covers, then link or refer to the authorized device-specific reference where instructions differ.
How often should employees follow this routine?
Follow it each time you use a shared device, especially before beginning work and before leaving it. Check that the approved start screen has returned after signing out. Device owners should review the page when sign-in or sign-out instructions, support routes, or device configurations change.
What should someone do if another person's information is already visible?
Do not open, inspect, or continue the previous user's work. Use the organization's approved local reporting route and describe the device location, what you observed, and when. Avoid putting another person's private information in an open message or photograph.
Does this template satisfy a particular privacy or security regulation?
The page is an operational reminder, not a legal or technical compliance guarantee. Its sample advice supports careful shared-session use, but applicable obligations depend on the organization's systems, data, location, and policies. Have the appropriate privacy or security owner verify local requirements and approved procedures.
What is a common sign-out mistake this page helps prevent?
Closing a window or walking away does not prove that the application or shared device session has ended. Use the relevant sign-out controls and wait for the approved start screen. If sign-out does not complete or information remains visible, contact the designated support role.
What should we customize before publishing the page?
Replace the fictional scope notice and worked example with confirmed information for your organization. Specify the approved sign-in method, device-specific instructions, designated support role, and local reporting route. Keep the general warning not to use another person's open session, and identify an owner who will update the page when procedures change.
Does the page connect to live device monitoring or create a support ticket?
No. The sample notice is authored information, not live device or incident monitoring, and the page structure does not establish a ticketing integration. The template names support roles but does not supply verified contact details or a working reporting link; add these through your organization's approved setup.
How does this page compare with an informal reminder?
It puts the routine in a visible sequence and gives a concrete example of what to do when a prior session remains open. Unlike a brief ad-hoc reminder, it also distinguishes application sign-out from returning the shared device to its start screen and identifies who can help. It still needs local instructions to serve as an actionable support reference.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Shared Device and Kiosk Basics ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
