Facebook Access vs Task Access: The Difference Shows Up the Day Someone Leaves
- Facebook access lets someone switch into the Page and manage it on Facebook itself. Task access only lets them manage it from tools like Business Suite, Ads Manager, or Business Manager — they can't s
- That's why the classic symptom is 'my agency can schedule posts and run ads but can't reply to comments as the Page.' That's not a bug, that's task access working as designed.
- Facebook access splits further into full control and partial control, so 'has Facebook access' isn't one permission level — ask which.
- The moment this actually costs money is offboarding: nobody audits access until a contractor leaves, and the person who granted it is often the one who left.
Your agency says they can't reply to comments as the Page. You check, and they're clearly in there — they scheduled three posts this morning and they're running your ads.
Nothing is broken. You gave them the wrong one of two things that sound identical.
The Actual Distinction
From Facebook's help documentation on Page access, the two access types are defined by where the person can work:
- Facebook access — comes with full control or partial control, and people can switch into the Page and manage it on Facebook or through other Facebook tools. Content, messages, comments, ads, insights, events.
- Task access — people can manage the Page from other tools such as Business Suite, Creator Studio, Ads Manager, or Business Manager, but they can't switch into the Page or manage it on Facebook.
The phrase doing all the work is "switch into the Page." That's the act of becoming the Page — commenting as it, appearing as it, being it in a thread. Task access never grants that, no matter how many individual tasks are ticked on.
Task access is permission to work on the Page. Facebook access is permission to be the Page. Every confusing symptom in this area comes from expecting the first to include the second.
Diagnose It by Symptom
You usually don't find out by reading a settings screen. You find out because something specific doesn't work. Match yours:
- Can schedule and publish, can't comment as the Page → task access. Publishing is a task; appearing in a thread as the brand requires switching in.
- Can run ads, can't post organically → task access with only the ads task enabled. Ads and content are separate tasks.
- Can do everything but can't add another person → Facebook access with partial control. Granting access is the classic full-control-only power.
- Sees the Page in Business Suite but not in the Facebook app's account switcher → the clearest tell of all. Task access is tool-side only, so the switcher is exactly where it's invisible.
- Was fine last month, broken now → someone's access was changed, or the Page was moved into a different business portfolio. Access rides on the portfolio.


Which One Should You Actually Grant?
The default instinct is to grant the strongest thing so nobody complains. That instinct is what produces Pages with eleven admins, four of whom left the company.
A workable default:
- External agencies and contractors → task access, with only the tasks their contract covers. They almost never need to be the brand; they need to publish, schedule, and report.
- Community managers → Facebook access with partial control. Replying as the brand is the job, so they need to switch in. They do not need the ability to hand the Page to someone else.
- Facebook access with full control → two people, both internal, both permanent. One is a single point of failure; three is a governance problem.
- Nobody gets access "temporarily." Temporary access is permanent access with an intention attached.
The specific asymmetry worth internalising: task access can spend your money but can't speak for you. Someone with ads-task access can burn your budget while being unable to post a comment. If your mental model is a single dial from "less" to "more" power, that combination looks impossible — which is exactly why people mis-grant.
The Day It Actually Costs You
Nobody audits Page access on a calm Tuesday. They audit it the day a contractor's relationship ends badly, or the day an employee leaves and takes an account with them.
And there's a trap built into that moment: the person who granted access is frequently the person leaving. If they held full control and nobody else did, removing them is not something you can just do.
Three things worth doing this week, none of which take long:
- Open the access list and read it out loud. Name by name. You will find someone.
- Confirm at least two internal people hold full control — and that one of them isn't a personal account tied to someone's old email.
- Write down who has what, outside Facebook. A one-line note per person. The list inside Facebook doesn't tell you why anyone has access, and "why" is the only thing that lets you safely remove it later.
Why This Gets Worse With Scale
One Page, three people — a spreadsheet handles it. Twelve Pages across four brands and a rotating bench of freelancers is a different problem, and it's the one that quietly eats agencies.
There's also a structural point worth naming: every model where you grant a third party access to your Page is a model where the permission is the product. It has to be granted, tracked, and revoked, and the revoking step is the one that never happens on time.
That's a deliberate design choice in how we built NoobClaw: you log into your own accounts, in a local browser on your own machine, with each account kept in its own session. There's no access to grant to us and nothing to revoke, because the credentials never leave your side. The tradeoff is honest — it means your machine has to be running, and the login has to be valid. But it does mean that offboarding a contractor is a question about your own machine, not about someone else's dashboard.
If your problems are more about cross-posting behaviour than permissions, that's a separate diagnosis — see why cross-posting between Instagram and Facebook stops working, which has nothing to do with access levels and gets misdiagnosed as a permissions issue constantly.
One Thing This Is Often Confused With
Page access is not the same as posting capability, and the two get diagnosed as one problem. If posts are going out but landing wrong — cross-posted to the wrong surface, or duplicated — that is a sharing-settings issue, not a permissions issue. See how cross-posting settings live in three separate places, none of which are in the access list. Checking permissions first is the reflex; it is almost never the cause.
If you manage Pages for more than one brand, the same reasoning applies one level up — see how platform-side account caps and manager limits interact for a worked example on a different platform; the pattern is identical, and it is the reason access audits should follow the asset, not the person.
The Handover Checklist Nobody Writes Until It's Too Late
Access problems are almost never discovered while things are calm. They're discovered during a handover — and handovers are exactly when nobody has time to work out how Meta's permission model is structured. So write this down once, now:
- Who holds full control, by name and by personal account. Not "marketing" — a person. Full control is attached to individual profiles, and individual profiles leave companies.
- Which business portfolio owns the Page. If you can't answer this, you don't actually know who controls the asset, regardless of who appears in the access list.
- Which email each full-control holder's personal account uses. Recovering a Page through someone's defunct work email is a support-ticket-shaped problem you don't want.
- What each external party has and why. One line each. "Why" is the field that lets a future you remove access without a nervous phone call.
- A removal date for every contractor entry. Even a made-up one. An entry with a date gets reviewed; an entry without one becomes permanent.
This document is boring and takes twenty minutes. It is also the only thing standing between you and a Page you can see but cannot administer.
FAQ
Can someone with task access delete my Page?
Deleting a Page is not an ordinary task — it sits with full control. That's the clearest practical reason to keep external parties on task access: the destructive actions aren't in their reach at all, rather than being in reach and merely discouraged.
How do I give someone task access to my Page?
It's granted from the Page's access settings, where you pick the access type and then the specific tasks. Facebook maintains a separate help article on giving, editing or removing Page access. The important part is the first choice — access type — because the task checkboxes can't add the ability to switch into the Page later.
Why can't my agency reply to reviews or comments?
Almost certainly task access. Replying publicly means appearing as the Page, which requires switching in. If replying as the brand is part of their job, they need Facebook access — and at that point, partial control is the right level.