Skip to main content

You Can't Fire Someone for That Facebook Post: What the NLRA Means for Your Social Media Policy

Published Last updated 10 min readMike ThriftMike Thrift
You Can't Fire Someone for That Facebook Post: What the NLRA Means for Your Social Media Policy

Imagine this: it's 9 p.m., and one of your employees posts on Facebook that your company's pay is a joke and the new schedule is unfair. Two co-workers pile on in the comments. A third shares the post with a "this is our life now" caption. By morning, a customer has screenshotted the whole thread and tagged your business page. Your first instinct is to fire everyone involved for disparaging the company. Acting on that instinct could cost you back pay, a reinstatement order, and a federal case — even though you don't have a union and never will.

The reason is a 90-year-old labor law that covers far more small businesses than most owners realize, and it protects employees who complain about work together — online just as much as around the water cooler.

The Law That Covers You Even Without a Union

Section 7 of the National Labor Relations Act (NLRA) gives employees the right to engage in "concerted activities for the purpose of collective bargaining or other mutual aid or protection." The key point small employers miss: these rights belong to union and non-union employees alike. You do not need a union workforce, an organizing drive, or even a single union sympathizer on staff for the law to apply to you.

The National Labor Relations Board (NLRB), the federal agency that enforces the Act, has brought cases against non-union employers for firing workers over social media posts. Remedies can include reinstatement and back pay — and the reputational damage of a public enforcement action on top.

Does the Board have jurisdiction over a business your size? Probably. The NLRB asserts jurisdiction over retailers with at least $500,000 in annual gross volume, and over non-retailers with at least $50,000 in goods or services flowing in or out of state — thresholds most operating small businesses clear without thinking about it, since buying supplies, software, or inventory across state lines counts. Unless you are in an excluded category such as a government employer or a tiny purely local operation, assume the Act covers you.

What Counts as Protected Concerted Activity

For an employee's social media activity to be protected, it generally needs two ingredients: it must be concerted, and it must be for mutual aid or protection around wages or working conditions.

Concerted means together, not solo

The Board defines concerted activity as action engaged in "with or on the authority of" other employees — not solely by and on behalf of the employee alone. In practice, that includes:

  • Two or more employees discussing pay, schedules, safety, or supervisors online together.
  • One employee posting a work complaint that draws supportive comments, shares, or discussion from co-workers.
  • An individual employee trying to start group action — for example, urging co-workers to sign a petition about the new attendance policy.
  • An individual bringing a genuinely shared group complaint to management's attention.

The classic pattern the Board has protected looks like this: an employee posts a complaint about a supervisor's treatment of the staff, co-workers respond with their own similar complaints, and the thread becomes a group discussion of working conditions. When the employer in that scenario fired the posters, the Board held the firings unlawful because the thread was protected concerted activity. Group griping with co-workers participating is the core of what the statute protects.

It has to be about work

The second ingredient is subject matter: the activity must concern wages, hours, or other terms and conditions of employment — pay rates, schedules, overtime, safety, supervision, benefits, workload. A thread where your crew debates whether the new shift rotation is unfair is squarely within the zone. A thread where they argue about last night's game is not.

What Is Not Protected

Not every angry post is shielded. Understanding the boundaries matters just as much, because this is where lawful discipline lives.

Mere griping. A solo complaint with no co-worker involvement and no call to action is generally unprotected. An employee who vents to family members about the bonus policy, without seeking anything from co-workers, is engaged in personal griping — not concerted activity. The line often turns on whether co-workers joined in or were invited in.

Disparagement disconnected from working conditions. Harsh criticism of the company's product or service, made to outsiders with no reference to a labor dispute or working conditions, can lose protection. There is a meaningful difference between "our schedules are dangerous and understaffed" (working conditions) and "our food is garbage, eat elsewhere" (naked disloyalty). That said, this is a fact-specific line courts and the Board draw carefully — mixed posts that combine criticism with a working-conditions message often stay protected.

Conduct that crosses the line. Even concerted activity can lose protection if it becomes so flagrant, violent, or extreme that the employee is unfit for continued service. True threats, violence, and deliberate falsehoods are unprotected. Rudeness and disrespect alone, however, do not strip protection — an otherwise protected complaint does not become fireable just because it is profane or insulting to a manager.

Illegal activity. Strikes or protests involving unlawful conduct, and posts that disclose legitimately confidential information such as trade secrets, sit outside the statute's protection.

Because these lines are fact-dependent and the penalty for guessing wrong is a federal unfair-labor-practice charge, treat every discipline decision involving employee speech about work as a stop-and-think moment, not a reflex.

Your Handbook Is Probably Overbroad

Here is the part that surprises most owners: the risk is not only in firing someone. Under the Board's current standard, merely maintaining an overbroad policy can itself violate the law — even if you have never enforced it against anyone.

In its 2023 Stericycle decision, the Board adopted a test that presumes a workplace rule unlawful if an employee could reasonably read it to chill Section 7 activity. The employer can rebut that presumption only by showing the rule advances a legitimate and substantial business interest and that no narrower rule could do the job instead. That replaced a more employer-friendly test, and it means many ordinary handbook provisions deserve a second look:

  • Blanket no-disparagement or "be respectful" clauses. A rule barring "negative" or "disrespectful" comments about the company can reasonably be read to ban protected complaints about pay or supervisors.
  • Overbroad confidentiality rules. Prohibiting employees from discussing "confidential company information" without carving out wages and working conditions chills exactly the conversations Section 7 protects. Pay secrecy policies are a perennial enforcement target.
  • Sweeping social media bans. Rules requiring employees to get approval before posting about the company, or banning all workplace discussion online, are classic violations.
  • No-recording or no-photography rules. Depending on wording and context, these can be read to bar employees from documenting working conditions or picketing.

Note that tacking on a generic savings clause ("nothing in this policy limits your rights under the law") does not reliably fix an otherwise overbroad rule. The Board looks at how an employee would reasonably understand the rule as a whole. Enforcement posture at the agency's General Counsel level has shifted somewhat toward narrower pursuit in 2025–2026, but the Stericycle standard itself still governs decided cases — so audit your handbook against it regardless of headlines.

Building a Social Media Policy That Holds Up

You are allowed to have a social media policy. You just need one written with the statute in mind. Work through this checklist with an employment attorney before your next handbook update:

Say what the policy is really for

Anchor each restriction in a specific, legitimate interest: protecting trade secrets and customer data, preventing harassment and threats, keeping employees safe, complying with industry regulations. Vague appeals to "protecting our reputation" read as bans on protected criticism.

Carve out Section 7 activity explicitly

State plainly that nothing in the policy prohibits employees from discussing wages, hours, or working conditions with co-workers, online or off — and make sure the rest of the policy is consistent with that promise. A carve-out surrounded by contradictory bans will not save the bans.

Regulate conduct, not complaints

You can prohibit threats, violence, harassment of co-workers, disclosure of trade secrets and customer data, and posting while on duty in safety-sensitive roles. You generally cannot prohibit complaining about work, sharing pay information, or talking to co-workers about a supervisor.

Train the people who enforce it

Most violations happen at the moment of anger: a manager sees the post, feels betrayed, and fires off a termination. Train every supervisor that employee speech about pay, schedules, staffing, and supervision is legally sensitive territory, and require a pause-and-escalate step — ideally a review by you and your employment counsel — before any discipline connected to social media activity.

Pause before you punish

When a post surfaces, ask three questions in order: (1) Did co-workers participate or was group action invited? (2) Is it about wages or working conditions? (3) Does it involve threats, violence, deliberate lies, or disclosure of genuine secrets? If the answers are yes, yes, no — stop and get legal advice before acting. Document the analysis, not just the post.

Keep state password-privacy laws in mind

Many states separately bar employers from demanding employees' social media usernames or passwords or requiring access to private accounts. Investigate using only what is publicly visible or voluntarily shared — and never retaliate against someone for refusing to hand over credentials.

The Bookkeeping Side: Document Everything, Expect Back Pay Math

Labor disputes create accounting work, and sloppy records make every outcome worse. Three habits pay for themselves:

Keep personnel files that tell the story. Every warning, performance review, schedule change, and policy acknowledgment should be dated, signed, and filed. If a termination is ever challenged, the difference between "fired for the Facebook post" and "fired after three documented attendance violations" lives entirely in your files. Store signed handbook acknowledgments — including the social media policy — where you can actually find them.

Know what a back-pay order costs. If the Board orders reinstatement with back pay, you owe the earnings the employee would have received, typically offset by interim earnings — computed quarter by quarter from payroll records. That computation is only as good as your timekeeping and payroll archives, so treat retention of payroll records as litigation insurance, not clutter.

Track policy-related costs separately. Legal review of the handbook, manager training time, and any settlement or compliance costs belong in their own expense categories. When the same issue recurs, you want to see exactly what it costs — clean categorization turns a painful lesson into a budgeted line item instead of a mysterious margin leak.

Keep Your Workplace Records Organized From Day One

Handling employee speech issues well comes down to two things: knowing where the legal lines are, and having records clean enough to prove you stayed inside them. Clear policies, documented decisions, and well-kept payroll and personnel files protect you far more than a quick trigger finger ever will. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.

Share this article