Skip to main content

Why Shared Logins Are a Serious Risk

If your team uses a shared email like [email protected], you lose accountability, traceability, and security.

Updated over 6 months ago

No Way to Track Who Did What

When multiple people use the same login, any action in Hera—like disabling an Associate, changing vehicle assignments, or editing notes—is logged under one generic name. Hera cannot tell who actually performed the action.

This becomes a problem when:

  • A mistake is made

  • A record is missing or modified

  • A customer complaint needs investigation

  • Something needs to be audited


Real Scenario: Lost Accountability

Two dispatchers share a central computer. In the morning, one disables an Associate and clears a counseling. Later, the second dispatcher logs in and reissues the counseling thinking it was an error. Both actions are logged under "[email protected]."

Leadership has no way of knowing who made which decision. If documentation is missing, if a photo log is incomplete, or if there's a compliance issue, there is no audit trail to fall back on. You're left guessing.


Former Employees May Still Have Access

Even if a shared login is only used on a single device, a former employee who remembers the password or has leftover access can still log in. We’ve seen cases where ex-employees:

  • Deleted data

  • Modified records

  • Accessed Associate information

  • Operated unnoticed, since their actions looked like any other team member

In these situations, Hera cannot trace activity or recover accountability. The damage is done.


Best Practice: Use Personal Logins

We strongly recommend creating unique logins for each team member, even if they are using the same computer. This gives you:

  • Full traceability of actions

  • The ability to immediately disable access when someone leaves

  • Cleaner logs and accountability for mistakes

  • Protection against unauthorized access

Avoid using shared emails like [email protected] or [email protected]. Each person should have a login tied to their personal work email.


You are welcome to leave your current process as is, but we want to stress that we have seen these issues firsthand. When something goes wrong due to a shared login, there is nothing Hera can do to assist in identifying the source or reversing the damage.

Did this answer your question?