It happens more often than you'd think. An employee has a bad day, opens Facebook, and types out exactly how they feel about the boss, a coworker, or the company. A few hours later, someone's forwarded a screenshot to HR.

The question that follows is almost always the same: can the company actually fire someone over this? The Supreme Court has already answered it — and the case is worth knowing in detail, because the reasoning tells you exactly where the line sits.

The short answer

A Facebook post, by itself, is not an automatic ground for dismissal. Employees still enjoy security of tenure under the Constitution and the Labor Code, which means an employer needs a valid cause and a fair process before anyone can be let go — a social media post included. Whether a specific post clears that bar depends on a handful of factors the Court has already spelled out.

The case that settled it

In Interadent Zahntechnik Philippines, Inc. v. Simbillo (G.R. No. 207315, November 23, 2016), a finance and accounting manager posted a Facebook status venting about people at work who lacked "credibility" and "conscience," without naming anyone. The company connected the dots to an ongoing issue with the BIR and fired her for loss of trust and confidence — a ground the law reserves mainly for managers and employees who handle money, records, or confidential matters.

The Supreme Court sided with the employee. The post never named the company, never disclosed any confidential or corporate information, and wasn't clearly directed at anyone — it read, at most, as a vague expression of frustration. The Court's reasoning is the part worth remembering: loss of trust and confidence only justifies dismissal if the employee's act was willful — done knowingly and purposely, not just carelessly or thoughtlessly. Reading the worst possible meaning into an ambiguous post, and firing someone on that assumption, doesn't meet that bar. The dismissal was struck down, though the Court acknowledged the post was still careless enough to warrant a lesser penalty than termination.

What the ruling actually tests for

Strip the case down to its logic, and the Court was checking for four things before it would even consider the post a valid ground for termination:

Was there a clear, identifiable target? A post that names the company, a specific client, or a specific coworker is treated very differently from one that's vague enough to be about anyone.

Was it willful? The employer has to show the employee knowingly and deliberately meant to cause harm or breach trust — not just that the post was careless or poorly worded.

Was there actual disclosure or damage? Confidential information, trade secrets, or client data being revealed weighs heavily against the employee. Hurt feelings or embarrassment alone do not.

Does the employee's role matter? Loss of trust and confidence, specifically, applies with real force only to employees in positions of trust — managers, cashiers, anyone handling money, records, or sensitive information. For rank-and-file employees, the employer would generally need to point to a different just cause, like serious misconduct.

Flip any of these — a post that names the company outright, discloses real confidential information, or is written and shared in a clearly deliberate, calculated way — and the analysis tilts the other direction. That's not a hypothetical stretch; it's the same test the Court applied, just with the facts running the other way.

"Private" doesn't mean protected

A common misconception is that a "friends only" post is legally off-limits to an employer. It isn't. Once it's shared, screenshotted, or reported by a coworker, it's fair game for an investigation — the privacy setting affects how the post spread, not whether the company can act on what's in it.

Due process still applies

Even where a post is serious enough to justify dismissal, the employer still has to follow the two-notice rule: a written notice specifying the post and the charge, a real chance for the employee to explain, and only then a second notice of the company's decision. Skipping it, even when the post looks bad on its face, exposes the company to liability for nominal damages — separate from whatever happens on the substantive question of just cause.

Practical takeaways

For employers: don't react to a viral post by firing on the spot. Ask whether the post actually names or clearly points to someone, whether it discloses real confidential information, and whether the employee's role even makes loss of trust and confidence the right ground to invoke. Then go through the notice-and-hearing process regardless of how obvious the offense looks. A clear, written social media policy that employees have actually seen and signed also strengthens your position considerably.

For employees: a bad day and an angry post are human, but a post that names a company, client, or coworker — especially if you hold a position of trust — carries real risk, "friends only" setting or not. If in doubt, log off before you type it out.