Security at a Glance
Security at a Glance is a one-page employee reference with ten practical habits for safer work, plus a clear sample route to ask for help through the Service Desk app.
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 · Retail and hospitality · Manufacturing · Professional services · Education
Overview
Security at a Glance is a one-page employee reference built around ten workday habits and a sample help route through the Service Desk app. The fictional Northstar example covers account and sign-in safety, device locking, unexpected prompts, suspicious links and attachments, unusual payment or sensitive-data requests, approved sharing tools, updates, physical security, and prompt reporting. A separate callout explains what information to include when asking for help and what not to send, while a closing section identifies the need for an owner and review trigger.
Use this page when employees need a quick reminder they can scan during routine work, onboarding, or a shift handover. Its numbered list makes actions easy to find, and the callout places the sample support route near the relevant guidance. The page is a reference, not a reporting form, live integration, training course, or full incident-response procedure. It does not establish a specific response time, escalation chain, or local security policy.
Before publishing, have the security or policy owner validate each habit against current requirements and approved tools. Confirm that the Service Desk app route is available to office and frontline employees in every intended location, and add any confirmed urgent-response instructions through an authoritative source. Assign an owner and review the page when the policy, tools, or reporting route changes. Do not present the fictional Northstar wording as confirmed company policy or use the page in place of detailed procedures for specialized roles.
Standards & compliance context
- Treat the Northstar content as fictional sample guidance and validate it against applicable company policies and requirements before publication.
- Do not describe the page as a complete incident-response procedure or as proof of compliance with a particular law or security standard.
- Confirm that the approved sign-in, update, data-sharing, and reporting instructions are accurate for each intended location and role.
- Maintain accessible headings, readable text, and usable navigation in line with WCAG 2.1 AA expectations for employee-facing pages.
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
Security habits for every workday
This introduction clarifies that the Northstar example is a general reminder and that local requirements and approved tools may differ.
-
This fictional Northstar example is for office and frontline employees across locations. Use these ten habits as a quick reminder; local requirements and approved tools may differ. This page is sample guidance, not confirmed Northstar policy.
Ten practical security rules
These ten actionable habits cover common risks involving accounts, devices, requests, information sharing, updates, and reporting.
-
Pause when something feels unusual, and use the Service Desk app to ask for help. Use a unique password and approved sign-in protections Use a different password for each work account. Turn on the sign-in protections provided by your organization; do not use an unapproved tool to store or share passwords. Never share passwords or verification codes Do not give your password or a one-time verification code to anyone, even if a message or caller claims to be a manager or support staff. Lock your device when you step away Lock your screen whenever you leave a work device unattended, including during a short break or shift handover. Stop if a sign-in prompt is unexpected Do not approve an authentication prompt you did not start. Use the Service Desk app to report the unexpected prompt or ask what to do next. Check unexpected links and attachments Before opening a link or attachment, check whether you expected it and whether the request makes sense. If unsure, verify with the sender using a work contact method you already trust. Verify unusual payment or sensitive-data requests Before sending money or sensitive work information, confirm the request with the person through a separate, trusted work channel—not by replying to the request itself. Share work information only with approved people and tools Check the recipient and audience before sharing. Use organization-approved tools, and do not move work information to a personal account or unapproved service. Install updates through approved channels Apply device and software updates when prompted by your organization or its approved tools. If an update prompt seems suspicious or disrupts work, ask the Service Desk before proceeding. Protect devices and papers in shared spaces Keep work devices with you or secured when practical. Put away papers containing work information when they are not in use, especially in public or shared areas. Report loss, suspected scams, or accidental sharing promptly If a device is lost, you may have interacted with a scam, or work information went to the wrong person, contact the Service Desk through its available support or reporting route. Describe what happened and what you did; never include passwords or verification codes.
Need help? Open the Service Desk app
This callout explains how to describe a concern while keeping passwords and verification codes out of the report.
-
Use the app's available support or reporting route for a security question or concern. The correct app route and any urgent-response process must be confirmed by Northstar before this sample is published. Open the Service Desk app and choose the available route that best matches your question or concern. Describe what happened, when you noticed it, and any action you took. Do not include passwords or verification codes. Follow the instructions you receive through the Service Desk.
Keep this reference current
A named security or policy owner should validate the sample wording, confirm the reporting route, and revisit the page when its underlying guidance changes.
-
Report promptly Report suspected issues promptly through the Service Desk app and follow the instructions provided there. A quick reference, not policy This page is a quick reference, not a substitute for applicable company policies. Before publishing this fictional example Northstar's security or policy owner should complete these checks. Validate the wording Confirm the reporting route across locations and roles Set an owner and review trigger—for example, a change to the applicable policy, approved tools, or reporting route
How to use this template
- Copy the page and have the security or policy owner check each of the ten habits against current company policies and approved tools.
- Confirm the Service Desk app’s available support or reporting route for each intended location and role, and add only verified urgent-response instructions.
- Name the responsible page owner and define a review trigger tied to changes in policy, approved tools, or reporting routes.
- Publish the reference in a location employees can find, and introduce it during onboarding or team communications without treating it as a replacement for required training.
- Ask employees to use the applicable Service Desk route for concerns and to describe what happened, when they noticed it, and any action taken without sharing passwords or verification codes.
- Review the page when its trigger occurs, correct outdated wording or routes, and check that the guidance remains understandable to both office and frontline employees.
Best practices
- Keep the ten actions intact as short, observable habits, and link to detailed procedures only when a verified destination exists.
- Confirm the Service Desk route and any urgent-response process with the relevant owner before describing them as available to employees.
- Check that examples involving sign-in protection, updates, and approved tools match the organization’s actual environment.
- Preserve the instruction to verify unusual requests through a separate trusted work channel rather than replying to the original message.
- Tell employees what information is useful in a report and explicitly remind them not to include passwords or verification codes.
- Use the page as a quick reference alongside—not instead of—formal policies, incident procedures, or role-specific training.
- Assign a security or policy owner and review the page when policies, approved tools, or reporting routes change.
- Test the page’s readability and keyboard accessibility, and maintain WCAG 2.1 AA accessibility for this employee-facing reference.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who is this security reference for?
The fictional Northstar example is written for office and frontline employees across locations. It covers everyday actions such as locking devices, checking requests, and reporting suspected issues. Before publishing, confirm that the wording and reporting route apply to each role and location.
How often should we review the page?
Set a named security or policy owner and review the page when applicable policies, approved tools, or the reporting route change. You can also schedule a regular review according to your organization’s content-governance practice. The sample does not claim a review date or establish a required cadence.
Who should own and maintain this page?
A security or policy owner should validate the habits and confirm that the Service Desk route works for the intended audiences. The Service Desk team can verify the app route and the wording employees should use when reporting. Name the actual roles or teams before publishing so readers know where help and corrections come from.
Does this template establish a security policy or guarantee regulatory compliance?
No. It is a quick-reference example, not a substitute for company policy, role-specific procedures, or legal advice. Its advice should be checked against the organization’s approved tools and applicable requirements before use. Add links to authoritative policy pages if the intranet has confirmed destinations.
What should an employee do after a suspected scam or accidental disclosure?
The sample directs employees to report promptly through the Service Desk app’s available support or reporting route. They should describe what happened, when they noticed it, and what action they took, without including passwords or verification codes. The organization must confirm any urgent-response process and the correct app route before publication.
Can we customize the ten habits for different locations and roles?
Yes, but preserve the distinction between shared reminders and local requirements. Verify the approved sign-in protections, update process, support route, and any location-specific instructions with the relevant owner. If employees need materially different procedures, link to authoritative role or location pages rather than implying this general reference covers every case.
Does the Service Desk callout create an integration or automated reporting workflow?
No. The callout is page content that tells employees to open the Service Desk app and choose an available route. It does not itself submit a ticket, confirm receipt, or define an escalation path. Configure or verify the actual app route separately, and avoid publishing the sample as a working destination until confirmed.
How is this better than sending occasional security reminders?
A single, findable page keeps ten everyday habits and the help route together, so employees can refer back to the same guidance. Unlike an occasional message, it can be maintained as an authoritative quick reference with a visible owner and review trigger. It should complement—not replace—required training, detailed procedures, or incident-response instructions.
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...
-
Compare clinical communication platforms and workforce apps for hospitals. Learn how to reach frontline healthcare staff without EHR logins in 2026.
-
Reduce burnout among healthcare employees with 5 proven strategies to boost engagement, support wellbeing, and improve retention.
-
Discover proven physician engagement strategies that reduce burnout, improve patient outcomes, and strengthen health system performance. Practical tips for...
-
Clinical Staff Engagement with MangoApps: unify schedules, training, and HR self-service in one mobile app for frontline healthcare teams.
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Security at a Glance 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.