Management → BM Pages (/app/bm-pages). Owner and Head only — the Tech role and everyone else don't get here: this is where people's access to Pages changes.
What's on the screen
Your BM's own Pages ("own") and the Pages another business shared with it ("from a partner"). For each: whether launches can use it (AdFleet's token sees it), on which ad accounts it is the launch Page, and who holds which permissions on it. All of it is read with “Read from Meta” — at most once per 2 minutes per BM; one press reads permissions on at most 25 Pages, the next press reads on.
Connect to launches
Tick Pages and press “Connect the ticked ones”: AdFleet's system user gets the “Advertise” permission on them and they show up in the launch Page picker. Where it already has it, nothing is sent; AdFleet's own permissions are never lowered. Under “Launch Page for ad accounts” you can also make one Page the launch Page of chosen ad accounts of this BM — an unpublished Page can't be one.
Page roles
Only for people and system users already in your BM — AdFleet never invites anyone. Meta's permissions nest: Insights → Advertise → Moderation → Content → Full control. AdFleet never takes off the last human admin and never lowers its own system user. Full control is given, taken or lowered only by the team owner, with a separate tick on the confirmation step — here and in Roles & groups (there it is the Admin level on a Page, also through an asset group): a Page admin can give access to the Page to people outside the BM. Asking another business for full control — the owner only too.
Add a Page to the BM or request access
Meta's normal flows only. “Add to the BM” — for a Page no business owns; Meta won't hand over another BM's Page. “Request access” — Meta sends a request to the business that owns the Page; access appears only once it approves it in Business Settings. Up to 10 ids at a time.
How a change goes
Every action first shows the list: before → after, what is skipped and what a guard refuses. “Run” works for 15 minutes, once; if anything changed in Meta meanwhile, AdFleet shows the new list and sends nothing. Requests go one at a time, at most 50 per run, pausing when Meta's load is high; one operation touches no more assets than your plan's ad-account count. Every change is recorded in the journal.
The pages_manage_metadata permission
Needed only for changes on Pages. Without it the screen is view-only, and a launch Page for ad accounts can still be picked from the usable ones. To turn changes on — tick the permission on the system user, re-issue the token and replace it in Ad accounts (/help/system-user-token).
What AdFleet doesn't do
It never creates Pages or takes them out of a BM, never invites people or gives roles through Meta's Page roles around the BM, never takes anyone else's Pages.