Facebook Page roles aren’t showing because they were replaced by eight tasks

Someone new joined and you need to give them access to the Page. You go to Settings, you look for Page Roles, and it isn't there. You check under a different menu. You check on desktop instead of mobile. You search the help centre and the article that comes up is about something adjacent but not this.

This is the specific flavour of frustration where you're sure you've done this before — and you have. The panel existed. It's gone now, and it was replaced by something with different words.

What replaced it

Page permissions are now split into two categories:

• Facebook access — with full control or partial control. People with Facebook access can switch into the Page and manage it from within Facebook itself, the way an Admin used to.
• Task access — people can manage the Page from external management tools (Meta Business Suite, Ads Manager, Business Manager) but cannot switch into the Page or manage it on Facebook directly.

If you have Facebook access with full control, you can add, edit or remove anyone else's access at any time. That's the closest equivalent to the old Admin role.

The eight task names, from the developer docs

Here's a practical detour worth knowing, because it applies well beyond this one question. Meta's consumer help centre pages frequently return nothing but a title — we tried two of them for this article and both came back as empty shells. The developer documentation, on the other hand, is fully readable and considerably more precise.

The Pages API documentation names the tasks explicitly:

• <code>ADVERTISE</code>
• <code>ANALYZE</code>
• <code>CREATE_CONTENT</code>
• <code>MANAGE</code>
• <code>MANAGE_LEADS</code>
• <code>MESSAGING</code>
• <code>MODERATE</code>
• <code>VIEW_MONETIZATION_INSIGHTS</code>

And on what Admin means in the new model:

If a person is given Admin access to a Page in the UI, that person is able to perform all tasks on that Page.

So Admin didn't disappear — it became "all eight tasks at once." The old role names were bundles; the new model unbundles them.

When a help centre article returns an empty page, don't conclude the answer doesn't exist. Check the developer docs. Platforms document precisely for developers and vaguely for everyone else.

Mapping the old roles onto the new model

Rough equivalents, useful for deciding what to grant:

• Admin → Facebook access with full control. All tasks, plus the ability to manage other people's access.
• Editor → Facebook access with partial control, or task access including <code>CREATE_CONTENT</code> and <code>MODERATE</code>.
• Moderator → task access with <code>MODERATE</code> and <code>MESSAGING</code>.
• Advertiser → task access with <code>ADVERTISE</code> and typically <code>ANALYZE</code>.
• Analyst → task access with <code>ANALYZE</code> only.

Treat these as a starting point rather than an exact translation. The genuine improvement in the new model is that you can grant messaging without granting publishing, or analytics without granting anything else — combinations the old five roles couldn't express.

The one trap that catches everyone

It's this line: people with task access cannot switch into the Page.

What that looks like in practice is a new hire telling you they have access but "the Page doesn't show up." They're looking for it on Facebook, and it will never be there — their access only exists inside Business Suite and the other management tools. Nothing is broken. They were granted the category that doesn't include that ability.

So when you're granting access, ask one question first: does this person need to act as the Page on Facebook itself (replying as the Page in comments, posting from the Page identity in the app), or do they just need to get work done in the tools? The first requires Facebook access. The second doesn't, and giving out less is the better default.

If you're managing more than a couple of Pages

The unbundling is a real improvement for security, but it comes with an audit problem: eight tasks times N people times M Pages is a matrix nobody reviews voluntarily. Two habits that help:

• Write down the intended grant when you make it, not later. "Contractor, Page X, CREATE_CONTENT + ANALYZE, until the campaign ends" takes ten seconds and saves an hour in six months.
• Review on the way out, not on a schedule. Nobody does quarterly access reviews. Everybody notices when someone leaves. Tie the removal to the departure.

If you're running a lot of accounts, there's a broader structural point here: every platform has a different permission model and none of them share vocabulary. Facebook has eight tasks, other platforms have seats, brands, or workspaces. Tools that publish through your own logged-in browser sessions — the approach NoobClaw takes — sidestep the granting problem entirely for publishing, because there's no third-party app to authorise; but you still need this model for anything a human teammate has to do inside Facebook itself.

Granting access without over-granting

The old model had five names and most people picked Admin because working out the difference took longer than it was worth. The new model makes least-privilege genuinely practical, so it is worth two minutes:

• A social media contractor usually needs <code>CREATE_CONTENT</code>, <code>MODERATE</code> and <code>ANALYZE</code>. They do not need <code>ADVERTISE</code>, and they almost never need to switch into the Page on Facebook.
• A media buyer needs <code>ADVERTISE</code> and <code>ANALYZE</code>. Nothing else. This is the single most over-granted role in most organisations.
• A community manager needs <code>MODERATE</code> and <code>MESSAGING</code> — and this is the one case where Facebook access is often genuinely required, because replying as the Page in comments happens inside Facebook.
• An agency reporting analyst needs <code>ANALYZE</code> alone. Read-only access is a clean option now; it was not before.

The rule of thumb that survives all of this: grant task access unless someone has told you specifically that they need to act as the Page inside Facebook. Task access covers the large majority of day-to-day work, and it is dramatically less dangerous to hand out.

What happens when the only person with full control leaves

This is the failure mode that actually hurts, and it is worth checking before it happens. If exactly one person has Facebook access with full control and they leave, deactivate their account, or lose access to it, nobody remaining can grant anyone else access — and recovering a Page in that state is a support process, not a settings change.

The fix takes one minute: make sure at least two people have Facebook access with full control, and that at least one of them is tied to the organisation rather than to an individual's personal circumstances. Do it today, not during the handover.

Related reading

For posting constraints on Pages, see the Facebook Page post limit per day. If you were looking for Groups rather than Pages, that's a different and much more closed door — posting to multiple Facebook groups at once explains what happened there. On account counts, see how many Facebook accounts one person can have, and for the cross-posting side, when Instagram-to-Facebook cross-posting stops working.

FAQ

Where is the Page Roles page now?

It was replaced. Page access is managed through the Page's settings under the access section, split into Facebook access and task access. If you can't see the option to manage anyone at all, you likely don't have Facebook access with full control on that Page.

Why can my colleague not find the Page after I gave them access?

Almost certainly because they were granted task access rather than Facebook access. Task access works only inside Business Suite, Ads Manager and similar tools — the Page will not appear for them to switch into on Facebook.

Are the eight task names something I'll see in the interface?

Not in those exact words. The interface uses friendlier labels. The uppercase names are how the API expresses them, which is useful precisely because it's unambiguous — when the UI wording is vague, the task list tells you what capabilities actually exist.