IT at a Glance
IT at a Glance is a single-page employee support guide for finding the Service Desk, trying safe first checks, and preparing a useful request. It helps employees know what to do next without risking saved work or account security.
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: Retail and frontline operations · Healthcare administration · Manufacturing · Professional services
Overview
IT at a Glance is a service page example for employees who need to report an IT issue or request help. It opens with the Service Desk route, then groups low-risk first checks for an unresponsive app or device, an unavailable connection, and a sign-in problem. A request-preparation section tells employees to describe the affected app or device, work location, start time, impact, and exact error text while keeping passwords and verification codes out of the request. The final section names an example content owner and explains when the guidance should be checked.
Use this page when employees need a concise starting point before they contact support, particularly when the same basic questions recur across office and frontline roles. It is designed to orient employees and improve the information they provide; it is not a troubleshooting manual, incident response plan, device policy, or replacement for the authoritative Service Desk process. The Northstar organization and its support details are fictional, and the example URL is not a working destination. Confirm the real audience, Service Desk route, supported devices, security escalation path, owner, and review cadence before publishing.
Keep the first action easy to find and preserve the safety boundaries in the sample: employees should save work before restarting, avoid changing security settings without IT direction, and stop if account access may be at risk. If an employee cannot access Service Desk, this example directs them to ask a manager for the approved alternative; replace that instruction if the organization has a confirmed route. Review the page when support arrangements change and on the confirmed review cadence so it does not become a stale or misleading entry point.
Standards & compliance context
- Treat this page as orientation to support, not as evidence that an organization meets a particular security, privacy, or regulatory requirement.
- Have the security owner verify that sign-in advice, suspected-account-access escalation, and credential-handling instructions match company policy.
- Apply WCAG 2.1 AA accessibility practices to the published page, including descriptive link text, readable headings, keyboard access, and sufficient contrast.
- Confirm that the support route and any alternative are appropriate for the stated employee audience and locations; do not infer local coverage from the sample.
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
Start with Service Desk
This opening identifies the example support route and tells employees what context to provide while keeping credentials private.
-
For Northstar office and frontline employees For an IT issue or request, open the Service Desk app in MangoApps and submit a request. Service Desk is the example support route on this page; these Northstar details are fictional and must be confirmed before use. Include the affected app or device, your work location, what you were trying to do, the exact error message, and when the issue began. Do not include your password or verification code. If you cannot access Service Desk, ask your manager to help you find the approved company support route.
Choose your next step
The quick link offers the primary support action before employees read the optional first checks.
-
Open the app for support; use the checks below for low-risk issues. Open Service Desk Report an issue or request IT help in the Service Desk app.
Safe first checks
These scenario-based checks help employees try low-risk actions and recognize when to stop rather than risk work or account security.
-
Try only checks that will not risk saved work, data, or account access. A device or app is not responding If your work is saved and no update or installation is running, close and reopen the app. Restart the device only when it is safe to pause your work. Save open work before closing an app or restarting. If the problem returns, record the app name and the message you see. Submit a Service Desk request if you cannot safely continue. First check A connection is unavailable Check whether the device shows a network connection and whether other approved work apps also fail to connect. Use only a company-approved network. Move to a location where your approved network is normally available, if practical. Do not change network or security settings unless IT has instructed you to. Tell Service Desk your work location and which apps are affected. You cannot sign in Check that you are using your own company account and that the username is entered correctly. Never share a password or verification code. Do not repeatedly guess passwords or approve an unexpected sign-in prompt. If you suspect someone else has access to your account, stop and report it through the approved support route. Describe the sign-in error in Service Desk without including credentials. Stop if security is at risk
What to include in a request
The ordered steps help employees describe the issue, add useful context, and follow up without creating unnecessary duplicate requests.
-
These details help the support team understand the issue and next action. The response times and contact arrangements are not supplied here. Northstar must confirm them in its Service Desk app and support guidance before publication. Describe what happened Name the app, device, or service and the task you were doing. Copy the exact error text if one appeared. Add work context Include your work location, when the issue began, and whether it affects one person or a work group. Do not include passwords or verification codes. Follow up in Service Desk Use the request details and any available updates in the Service Desk app. Add new observations to the existing request when possible instead of creating duplicates.
Who owns this guidance
This section makes ownership, the review trigger, and the example alternative support route visible for confirmation before publication.
-
Owner Northstar IT support team (fictional example). Review cadence The IT content owner should check this page whenever the Service Desk route, supported devices, or troubleshooting guidance changes, and at least quarterly as an example review cadence. Confirm the owner and cadence before publishing. Help route Use the Service Desk app for IT issues and requests. If you cannot access it, ask your manager to identify the approved alternative; no email address or phone number is supplied in this example.
How to use this template
- Confirm the intended employee audience, supported locations, devices, approved networks, and the authoritative support route with the IT content owner.
- Replace the fictional Service Desk name and invalid sample URL with a verified company destination, or remove the link if no approved destination is available.
- Check each first-check instruction against current IT and security guidance, including when to stop troubleshooting and how to report a suspected account compromise.
- Publish the page where its intended employees can find it, and test the Service Desk link and any access limitations from an employee view.
- Ask employees to include the affected app or device, location, start time, impact, and exact error text in a request without sharing credentials.
- Assign a confirmed role to review the page when support arrangements change and on the organization-approved cadence, then correct stale routes or instructions.
Best practices
- Put the verified Service Desk destination first so employees can reach support before reading optional troubleshooting detail.
- Keep first checks limited to actions that preserve saved work and do not change network, device, or security settings.
- Tell employees to save open work and confirm no update or installation is running before closing an app or restarting a device.
- Ask employees to report the exact error, affected app or device, work location, start time, and whether other people are affected.
- Repeat the instruction never to include passwords or verification codes wherever the page explains what to submit.
- Provide a confirmed alternative route for employees who cannot open Service Desk, rather than leaving them to guess.
- Name an accountable content-owner role and confirm a review cadence and change trigger before publication.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who is this IT support page for?
The example is written for Northstar office and frontline employees, but Northstar is fictional. Before publishing, confirm which employee groups, locations, and devices the support route covers. If different groups use different support channels, state the scope clearly or link to their authoritative guidance.
How often should the page be reviewed?
The example suggests checking the page at least quarterly and whenever the Service Desk route, supported devices, or troubleshooting guidance changes. Confirm that cadence with the IT content owner before publishing. Update the page sooner if employees can no longer reach the stated support route.
Who should own and maintain this guidance?
The sample names the Northstar IT support team as the owner, but that team and its responsibilities must be confirmed. Assign a role that can verify the Service Desk route and approve changes to the safe first checks. Give employees a clear correction or help route, without inventing contact details.
Does this template satisfy a particular IT or security regulation?
No: the page is an employee support guide, not a compliance certification or a complete security procedure. Its sample advice discourages sharing passwords and verification codes, repeatedly guessing passwords, and changing security settings without IT direction. Have the appropriate security or compliance owner check the finished guidance against applicable company policies and requirements.
What should employees do if the issue could be a security incident?
The sample tells employees to stop if they suspect someone else has access to their account and report the concern through the approved support route. Confirm and publish the organization's actual security incident route, especially if it differs from the Service Desk. Do not tell employees to continue troubleshooting or include credentials in a request.
What needs to be customized before this page goes live?
Replace or verify the fictional Northstar audience, Service Desk app name and route, support ownership, and review cadence. Confirm supported devices, approved network terminology, and the alternative route for employees who cannot access Service Desk. The sample link uses an invalid example address and must be replaced with a verified destination or removed.
Does the template connect to Service Desk or create support requests?
The page includes a sample quick link and instructions for using a Service Desk app; it does not establish a working integration or submit requests. The example URL is not a live support destination. Configure a verified company link and confirm that employees have the appropriate access before publishing.
How should we roll this page out to employees?
First verify the support route, scope, owner, and security guidance with the responsible IT roles. Replace the example link, then test the published page from the employee experience and confirm that the route is reachable for its intended audience. Tell employees where to find the page and review feedback for confusing steps or outdated details.
Why use this page instead of sending ad hoc IT instructions?
The page gives employees one place to find the support route, low-risk first checks, and the details to include in a request. It also identifies ownership and a review trigger, reducing reliance on scattered messages that can become stale. Keep the authoritative support process in Service Desk or its approved documentation, and use this page to orient employees to it.
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 IT 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.