r/ITdept • u/Popular_Walrus348 • 1h ago
r/ITdept • u/geeklimit • Nov 18 '23
Yes, your work can see what you do on their computer, and other questions [READ FIRST]
Due to the number of repeat questions around the topic of using work resources to do personal business, or generally questions around 'what can my work see', I've created this sticky to answer these and similar questions:
First, and most importantly:
/r/itdept is a place where IT workers come to talk to / ideate with / vent to each other, as mentioned in the sidebar. It's not a place for non-IT people to ask IT questions.
There are many, many places on Reddit to get IT help, depending on what you're asking for help on - use the sitewide search and use one of them, there are many people waiting to help you with your issue.
Second, to answer common questions:
Many of these questions come from having the wrong perspective around a person's usage of property and data belonging to the business they work for. The reality of your employment situation is as follows:
- It's not 'your computer'. It belongs to your workplace. They allow you to use it to do your work.
- Businesses have a lot of risk and liability. It's their right to know where their data is and how their equipment is being used. Where their data is, who can see it, and what their employees are doing or saying as an agent of the company is a huge concern, and they are within their rights to protect themselves.
- Some choose to monitor this to protect themselves, and some don't. Assume yours does. This monitoring applies to anything put into the computer with the keyboard or mouse/touchpad, all data going to/from the computer - including information about where it's going to and from, everything stored on the computer and any connected storage device, and anything stored under or done within any cloud service your workplace provides.
- None of this matters, because you should only use your work-issued equipment for work. Don't check your personal mail (or use work mail for personal things!), don't do online shopping, don't do your banking. Don't exist for your work as anything other than an employee, and you don't have anything to worry about.
Finally, and most importantly, something you need to understand about your local IT department that nobody will ever tell you:
It's likely that only one in 10,000 IT people are at all interested in what you're doing on your laptop, or if you're even doing your job at all - and they should be (and often are) fired for it, because they're probably violating the trust and faith the job requires to stick their nose where it doesn't belong. That's not IT's business or responsibility, and most of us want to be left alone when it comes to stuff like that.
It's HR and your manager's job to make sure you're productive and to manage you well. Frankly, many managers are quite terrible at their job and want a technological magic bullet to make up for their shortcomings. They're not bad people, this desire for a "solution" or a tool to "help them manage better" comes from the same place as their understanding of the problem: they don't know what they're doing, and it's easier to point at a "missing tool" that is "needed" than reflect and admit where the true deficits are, even to themselves. People often think of this as a victimless situation, because they're not blaming IT, they're just "sharing their amazing insight" into what's needed for the business, and "partnering with IT" to "fix it".
Most IT people hate this, both because it uses us to cover up other people doing their job poorly (something we're not allowed to do ourselves) but also because we're generally the type that believes that people should get what they deserve, both positively and negatively. Many IT people change careers because of the depression that comes from dealing with this. You'd be shocked by how many former technology people have gone "Stardew Valley" and are quite happy talking to a row of carrots instead of dealing with this any more.
By and large, we're also a very logical group of people. Generally, something will work when it's done a certain way in IT, and it doesn't work (or has significant downsides) when you don't do it that way. That's how IT systems work - there's a right way for a desired outcome, and the other ways are generally wrong based on what the desired outcome is.
We tend to know immediately that the problem is with your manager, or other underskilled "decision makers" in the organization, and that their idea is bad. This is very common when someone is looking for a technical solution to a non-technical problem. Unfortunately, we frequently will have a non-technical hand-shaker and yes-sayer leading our department, the same as you do, and we don't get the support we need to ask the business to exercise stronger critical thinking instead of complicating the IT environment with the product of inadequate management of human resources.
This usually leads to a system, process or policy that is either generally offensive to people they should consider as human beings, developing a system that attempts to solve problems that should be solved by non-technical means, and/or generally making our job more complicated and difficult to manage than it already is.
We're aware that this will be the case before, during and after the request gets put in, and the reality that waits for us for the forseeable future- but that is regrettably part of the job. It's not all doom and gloom, though - these darker parts sit alongside amazing opportunities that give us the chance to use our skills to create enormous value, extreme satisfaction at a job well done for thousands (or millions!) or people, great camaraderie with our IT coworkers who are there "in the trenches" with us, and a decent paycheck for our time and effort.
All this is a significant amount of background to truly understand where we're coming from, but results in this:
pre-tl;dr
If we're told to put in systems that record your screen or generally "spy" on employees, we'll either quit (and the next person will do it for them), or we'll do it to the best of our ability, but we like it even less than you do. We can't put them in halfway so they aren't effective - then the deficiency of good decision-making at the business turns into focusing on us and our ability to deliver working systems, no matter how asinine the reasoning was from poor managers. It's often better to perfectly implement the system and let them see that their proposed solution doesn't solve their perceived problem than to try and explain how bad of an idea it is (which they can't even accept, because it means admitting the problem is them!)
Our advice, by and large, is to ask questions in a non-suspicious way in regards to your privacy at work. Be clear on what the company expects and allows (get it in writing, the handbook is a good start) and don't work for places that want excessive monitoring systems from us - it's stuff like this that makes us leave, and you should too if it means a compromise in your self-respect.
But also realize that a minimal amount of monitoring is required by a business to manage its risk and liabilities, and this is fair for them to have in place / is often in place by default, whether they use it or not.
tl;dr:
Don't work for companies that have monitoring systems you don't feel comfortable with, and rest assured that IT people could not care less about what you're doing or not doing. It's not what we're in this career to do.
It's likely that nobody is watching anything, and it's only when the business already has decided that they want you gone that they'll go back through the records, looking for evidence to legally support that decision, regardless of what the real reason might be.
tl;dr edit: The exception to this is when you're blatantly violating company policy, the law, basic human rights, or other regulations. It should be assumed that doing intentional, egregious harm will trigger even the most basic of alerts in many systems, because that's the bare minimum any company should do to protect their assets and control their liabilities - and most companies have this by default with any standard software they've purchased.
r/ITdept • u/Flat-Sink-6771 • 16h ago
Do employers actually understand the value of their sysadmins and developers?
Something happened at work today that genuinely made me question how much management understands what their technical staff actually do.
For context, I’m responsible for a significant amount of scripting, integrations, database work, and automation across multiple enterprise systems. A lot of my day involves writing PowerShell, SQL, working with APIs, troubleshooting integrations, and developing solutions that keep different systems communicating with each other.
Recently, my organization started planning to provide AI subscriptions to employees for productivity purposes.
Which is great. I genuinely believe AI can make almost anyone more productive, regardless of their technical background.
But what bothered me was seeing someone in my own department, who doesn’t have a programming or development background, receive access to an AI tool while I, the person responsible for much of our scripting, integrations, and automation development, wasn’t even considered.
And that’s where my frustration comes from.
It’s not about a particular individual. They absolutely deserve tools that help them do their job better.
It’s about the fact that management seems to recognize the productivity benefits of AI for general administrative tasks but overlooks how much more efficiently someone working directly with code, databases, APIs, and enterprise integrations could operate with access to the same tools.
I’m not saying AI should replace technical knowledge. Quite the opposite. Understanding what you’re building, knowing how systems interact, and being able to troubleshoot your own code are essential.
But imagine having a tool that helps you troubleshoot complicated logic, refactor scripts, develop integrations, or work through unfamiliar APIs faster.
When you’re responsible for automations across multiple systems, even saving an hour on a single development task can make a significant difference.
And before anyone brings up security, I’m fully aware of the risks associated with exposing organizational data to external AI services. I’m talking about approved tools with appropriate safeguards, not throwing production credentials or sensitive data into a chatbot.
What really gets me is that so much of our work happens behind the scenes. When integrations run successfully, accounts get provisioned, databases communicate, and scheduled automations complete, nobody thinks twice about it.
But the moment something breaks, everyone suddenly remembers who maintains those systems.
I’m perfectly capable of doing my job without AI, and I’ve built plenty of solutions without it. That’s not the point.
**The point is that organizations seem eager to invest in productivity tools without always recognizing the people who could use those same tools to improve the infrastructure and processes the entire organization depends on.**
Maybe I’m just frustrated, but I’m genuinely curious.
Have other sysadmins or developers experienced this? Does your management understand the technical work you do, or do you feel like you’re constantly having to justify the value of your role?
r/ITdept • u/WingRevolutionary39 • 23h ago
How do you handle users refusing to put in Tickets
reddit.comr/ITdept • u/Callumwalsh-1422 • 1d ago
What’s your offboarding process for apps that don’t sit behind SSO?
Been thinking about offboarding lately, specifically the apps that keep their own local accounts outside AD.
Most of our process covers the obvious stuff. HR closes the record, the AD account gets disabled and SSO goes with it. Then a department head asked why someone who left months ago was still listed as an approver in our document management system, and it turned out the app has its own user list. Pulled it and a good chunk of the accounts belong to people who are gone. A few even show logins dated after their last day.
Nobody owns the app either. The team that bought it got reorganised away and the admin who ran it left a while back.
Someone suggested Anetac, someone else Orchid. Haven't demoed either. I'm more stuck on who should be responsible for cleaning this up, because right now nobody wants to own the app.
How are you guys handling offboarding for apps that don't have an owner anymore? Curious if there's an actual process for this.
r/ITdept • u/nharding-323 • 3d ago
what to choose unified endpoint management software or just an RMM for laptops and servers?
so got handed a project called "nified endpoint management" and not much else. For 1,600 users I mostly need to monitor, patch, and remote into laptops and servers from one place, Windows and Mac plus a few Linux boxes. I've been reading up on atera because it patches all three. Phones stay put in our MDM.
r/ITdept • u/Rhys_Callaghan4 • 3d ago
centralized signature deployment without giving users edit access in owa
company is around 600 seats. right now users have access to edit their outlook web signatures, and despite repeated policy emails, people keep tweaking fonts, pasting blurry jpegs, and deleting legal disclaimers. we want to lock it down centrally via azure ad attributes so it populates automatically when composing. trialing wise stamp right now since it pushes directly to outlook and owa without mail flow rules. curious if anyone has run into caching delays or quirks with the m365 add-in at this headcount.
r/ITdept • u/Consistent-Rich4676 • 3d ago
How do you gather requirements when key stakeholders are always too busy for meetings?
One of the biggest challenges I have been running into with requirements gathering isn't really the process itself, but getting the right people involved at the right time.
Some stakeholders have back to back meetings, others struggle to find time to prepare, and sometimes the person with the most important information isn't available when you need them. Waiting until everyone is free can slow the entire project down.
I have tried sending questions beforehand, arranging individual interviews, and organizing group workshops. Each approach has its advantages, but I'm still curious about what works best when dealing with particularly busy stakeholders.
How do you usually handle this? Do you prefer one on one conversations, async questionnaires, or group sessions?
I'm especially interested in hearing how you make sure important requirements aren't missed when some key people have very little time to contribute.
r/ITdept • u/InwoodTech-PDS • 5d ago
Two Internet Providers Are Not a Resilience Strategy
r/ITdept • u/clippyoffical • 5d ago
[OFFICIAL STATEMENT] Regarding Today’s Microsoft 365 Infrastructure "Incident"
reddit.comr/ITdept • u/gkar_of_Narn • 5d ago
Who causes the most loss of productivity in IT?
reddit.comr/ITdept • u/Ecstatic_Survey_9415 • 5d ago
Best Helpdesk System Features
Hello! I'm curious what helpdesk systems people have used, and which is the best. What features make it good? Do you feel like there's such a thing as too many features? I'm currently helping set up our (small) company's helpdesk and wanted some input.
r/ITdept • u/Different_Pain5781 • 6d ago
Does my company's DLP process need to change now that employees paste our data into generative AI tools?
Hi, I'm witnessing what feels like a security breach waiting to happen at my job. The employees at our company are constantly pasting source code, customer data and strategy documents into our AI tools and our DLP isn't catching or preventing any of this. What should we change in our process so these don't become a security risk?
r/ITdept • u/UPDF_Enterprise • 5d ago
What should teams check before choosing a PDF editor
For individual users choosing a PDF editor is usually about features and price. For organizations the decision is more complicated.
A few areas worth checking:
- Licensing and user management
- Compatibility across Windows, macOS, iOS, and Android
- OCR and redaction accuracy
- Document security and data handling
- Deployment and ongoing IT support
- Migration costs from an existing PDF solution
For teams that have recently evaluated or switched PDF tools: what was the most important factor in your decision?
r/ITdept • u/Wilsomjane86 • 6d ago
The amount of technical debt in some companies is genuinely surprising. Do you agree?
Some companies still rely on systems that nobody wants to touch because even a small change could break something else. It might seem easier to keep things running as they are, but eventually these workarounds can make maintenance and development much harder.
At what point should a company stop patching an old system and invest in fixing it properly? Is technical debt something teams should actively address, even when everything appears to be working?
r/ITdept • u/reid1_shaw • 6d ago
do u even allow personal accounts on the ai tool youve approved?
lets say the company pays for claude and gives everyone a work account. some people still prefer chatgpt or gemini, and some already have a personal claude account.
we're leaning toward a pretty strict allowlist and have been looking at Push and Bay. the first thing i'd want to check is what happens when someone opens an approved site and signs in with a personal account. the domain is allowed either way.
for teams that picked one approved tool, i'm curious whether you also restricted it to work accounts or kept personal sign ins open.
r/ITdept • u/Clean-Will-1858 • 6d ago
Engineers: How do you prefer Customer Success Managers (who aren't highly technical) to communicate technical problems to you?
reddit.comr/ITdept • u/Leo-Cole47 • 7d ago
outgrew hubspots free signature generator, what did you switch to?
been using hubspots free signature generator for our team. fine when there were a few of us. now every new hire or title change means I make a new one and email them the html to paste in there has to be a way to set a template once and just have it apply to everyone. I have see wise stamp and newoldstamp mentioned but no idea which is less hassle for a small team. what are you using?