Is IT support allowed to read employees' emails?

Technically it can, but it may only do so on a formal request from an authorised party (HR, security or legal) and under company policy. Even then, it looks only at what was asked for.

What if my manager asks me to do something that feels wrong?

Ask politely: "Has HR or security approved this?" If not, ask for the request in a ticket. Most wrong requests stop there, and the right ones go the official way with you protected.

Do IT support interviews ask about ethics?

Yes, often. A question like "A user asks for access without their manager's approval, what do you do?" shows the interviewer whether you can be trusted with the company's access. Answer with steps: refuse politely, point them to the official path, and record it.

IT Support Ethics: What to Do and What Never to Do

IT support can open any user's mailbox, see their screen, reset their password and reach every team's files. That power is what makes the job matter, and it's also why ethics is your most important skill, more than networking or Windows. These are the rules the technician everyone trusts lives by.

Why ethics matters so much in IT support

Most jobs give you access to your own work. IT support gives you access to everyone's. And since most of what you do goes unseen, the only thing between you and a bad decision is you.

You hold the keys to email, files, screens and accounts. Before opening any door, ask yourself these three questions.

1. Privacy: look only at what the ticket needs

If the ticket says "Outlook won't open", the contents of the emails are none of your business. If you're fixing a PC, you don't open the photos folder or personal files.

Before a remote session, ask the user's permission, tell them what you'll do, and let them close anything private.
If you see something by accident (a private message, a salary, a medical file), ignore it and don't mention it to anyone, not even your team.
Don't copy a user's files to your PC or a USB drive to "look at them later".

2. Passwords: never ask, never know

A rule with no exceptions: IT support never asks for anyone's password. If you need to get into their account, you reset it with their agreement, or they sign in themselves while you watch.

If a user tells you their password anyway, ask them to change it when you're done.
Never write passwords in the ticket or on a note stuck to the screen.
Teach users that anyone calling "from IT" and asking for their password is a scammer. It's the most common phishing trick.

3. Permissions: the least they need, with approval

The most dangerous thing a technician can do is grant access "to get it done". A friend in another team wants into the finance folder? Your manager wants to read a user's email? The answer is the same: every permission takes the official path.

The path for any permission: a formal request, the owner's approval, the least access that works, and a record. No shortcuts from the corridor.

Least privilege: they need to read? Don't give them edit. They need it for a week? Give it an end date.
Approval comes from the owner: the user's manager or the folder's owner, not the user.
If a manager asks for something sensitive (reading a user's email, tracking their PC), that's a decision for HR or security, not you. Pass it to them politely.

4. Honesty: say exactly what happened

Everyone makes mistakes. A good technician isn't one who never does; it's one who owns up fast. If you deleted a file by accident or switched off something you shouldn't have, tell your team straight away, while it can usually still be restored from backup.

Don't mark a ticket "resolved" before you've confirmed it.
Don't write steps you didn't take to make the ticket look tidy.
If you don't know, say "I don't know, I'll find out and get back to you". That sentence earns trust, it doesn't lose it.

5. Respect the user's work and time

Don't restart or close an app before asking: "Is anything unsaved?"
Back up first before anything that could wipe data: a format, a reinstall, a disk swap.
Never make a user feel stupid. They're the expert in their job, you're the expert in yours. Explain simply, without talking down.
Priority follows impact, not job title. A whole team that can't work comes before a manager's slightly faded screen.

6. Lines you don't cross

Don't install pirated or unlicensed software, even when a user asks.
Don't help anyone get around security controls (turning off antivirus, unblocking sites) without security's approval.
Don't use your access for yourself: checking a colleague's salary, unblocking a site for you, reading a friend's email.
If you find something wrong on a PC (stolen files, spyware), don't investigate it yourself or delete it. Report it to your manager or the security team and leave it as it is.

Real situations: what do you do?

Situation	The right move
A colleague says: "Give me access to the finance folder, I just need one file"	They raise a request and the finance manager approves it. Even then: read-only, for a set time.
A user tells you their password "to make it quicker"	You do the work, then ask them to change it in front of you.
A manager asks you to open an absent employee's mailbox	You pass it to HR or security, and open nothing without their written approval.
During a remote session you see a private message on the screen	You carry on with the task, ignore it, and never mention it.
You deleted an important file by mistake	You tell your team and ask for a restore from backup at once, and write what happened in the ticket.

Frequently asked questions

Is IT support allowed to read employees' emails?: Technically it can, but it may only do so on a formal request from an authorised party (HR, security or legal) and under company policy. Even then, it looks only at what was asked for.
What if my manager asks me to do something that feels wrong?: Ask politely: "Has HR or security approved this?" If not, ask for the request in a ticket. Most wrong requests stop there, and the right ones go the official way with you protected.
Do IT support interviews ask about ethics?: Yes, often. A question like "A user asks for access without their manager's approval, what do you do?" shows the interviewer whether you can be trusted with the company's access. Answer with steps: refuse politely, point them to the official path, and record it.