Evidence, channels & privacy · U.S. English
THE WORKFORCE COMMUNICATION EDITION / 01
A source-led review of LISA AUS, Mercury and eHub: what the public evidence supports, where it stops and what to verify next.
READ THIS FIRST
An official public link can help identify a service. It cannot authenticate a text message, confirm your access or establish that a work action succeeded. This review keeps those questions separate.
MESSAGE-EVIDENCE CHECKLIST / LOCAL ONLY
Choose three categories. Get specific verification steps, not a safety score. No message text, personal information, link inspection or account access.
Choose all three categories to see the next checks.
Follow the requested-action check first, then provenance, then subject. A genuine-looking message is not authenticated by this checklist. Nothing is submitted or saved by it.
Read or make an ordinary work response
Clarify whether this is information, an opportunity, a request or a confirmed outcome. Use the established employer process for any actual action. This checklist does not approve a response or certify a message.
Send a password, code, ID or private record
Do not send secrets or private records through an unverified message or this publication. Independently contact the employer’s established support or security channel about the request. If you already disclosed information, report that fact through the secure channel promptly.
Install software or grant a new permission
Independently verify the official app route and why the specific permission is required for your edition and feature. Do not install from a message attachment or grant access solely because the message uses the employer’s name.
I reached the service independently
An independently reached service is a stronger starting point than a supplied link, but this checklist has not inspected it. Confirm the notice concerns the right feature, period and account; do not treat source identity as proof of a completed action.
An incoming text, email or supplied link
Do not use the message’s own contact details as its proof. Reach the company or known employer contact independently. A familiar name, logo, timing or plausible work detail does not authenticate the sender.
A forwarded image or someone else’s report
A forwarded image may omit the original date, audience or conditions. Check the current employer source for the same subject. Do not request that a coworker share private account screens or forward their credentials.
Shift or work notice
Identify the specific offer or change in the current employer service reached independently. Ask which record governs if a notice and another view disagree. A public feature description does not establish your assignment.
Pay, schedule or contact record
Use the company-published employee directory to establish the relevant route. Verify the exact record in your own authorized context. Do not send pay statements or employee identifiers to this publication.
Official source: Allied Universal employee login directory ↗
App permission or privacy statement
Determine which edition and feature the question concerns. Read its applicable policy and ask the employer about unclear scope before treating a phone permission as an answer about all data practices.
Official source: Allied Universal Mercury privacy documents ↗
Two notices disagree
Compare subject, timing and status through the current employer record. Ask which instruction applies to the specific issue. Do not invent a synchronization delay or assume the most recently received message overrides everything.
Official source: Allied Universal employee login directory ↗
External links leave this publication. The checklist cannot authenticate a sender, confirm an account outcome or substitute for an employer’s urgent procedure.
THE READING LIST
Choose the uncertainty you need to resolve. Each article ends with sources and the limits of the evidence.
6 articles
Channel map
A source-led distinction among LISA, Mercury and eHub, with a practical test for claims that cross between them.
Read the article : LISA AUS: identify the channel before trusting the claimMessage risk
Review provenance and requested actions without pasting private messages into a checker or mistaking plausibility for authentication.
Read the article : A convincing message still needs an independent checkNotification choices
Separate delivery preferences, phone presentation and employer expectations before changing how work messages reach you.
Read the article : One quiet phone can hide several different settingsDevice privacy
A paired reading of the public Mercury documents, with questions that expose missing context without inventing a privacy guarantee.
Read the article : Read the app edition before the privacy headlineReliability
Compare scope, timing and status before treating a conflicting notice as a system failure or making a work decision.
Read the article : When two notices disagree, preserve the differenceSource review
Test a claim’s scope, date and evidence before repeating it as a fact about a private employee account.
Read the article : How much does a public page actually prove?LEAVING THIS PUBLICATION
Use Allied Universal’s published pages to establish the starting point for your question. External sites apply their own policies.