A volunteer who'd helped run our socials for a season at The Living Room was moving to Bozeman. Good terms, no drama. Taking her off the venue's Facebook Page should have been a two-minute job between two other things on a Tuesday.
Forty-five minutes later I was reading the same error message for the third time. Meta would not remove her from the Page because she was still assigned on the connected Instagram account. I went to remove her from Instagram. Meta would not remove her from Instagram because she was still assigned on the connected Page. Two systems, each pointing at the other, each refusing to move first. A real deadlock, not a glitch — I later found a small trade of frustrated posts from other business owners who'd hit the identical wall and given up, leaving a departed employee sitting in their business's account list indefinitely because nobody could find the actual door out.
What stuck with me wasn't the bug. Bugs get fixed or worked around. What stuck with me was that I couldn't answer, off the top of my head, who else had a key to that Page. Or the Instagram. Or the ticketing account that takes people's card numbers. I run a venue with rotating help — students, seasonal staff, volunteers who come for a run of shows and move on — and somewhere along the way "who can post as us" had quietly become a question nobody was tracking.
The liability nobody puts on a checklist
Every small operation accumulates access the same way a mudroom accumulates boots. Someone needed to post an event, so you added them. Someone was covering for a week, so you gave them the login instead of setting up a proper invite, because the proper invite takes longer and you were both standing there. None of it felt like a decision at the time. It felt like getting the job done.
Then a year passes. The person who covered that week left in March. The volunteer moved to Bozeman. The intern who set up your event ticketing graduated. And your business's public voice — the thing that answers a customer complaint in the comments, announces a closure, runs a paid ad against your name — is still reachable by three or four people who no longer have any reason to be near it, and one document, if you're being honest, that doesn't exist.
This is not a hypothetical risk. It's an inventory problem, and inventory problems get solved the boring way: you count what you have, you decide what each person actually needs, and you write it down where you'll find it again. Most owners skip straight past this because it isn't urgent until the day it very suddenly is.
It's the same failure I wrote about in the piece on decision rights — a role nobody defined turns into a role nobody can safely hand off. Access is the sharpest version of that problem, because an undefined decision just costs you time. Undefined access costs you control of your own accounts.
Start with an honest map, not a guess
Before touching a single setting, list every surface where someone outside you can act on your business's behalf. For most small operations that's shorter than it feels: the social accounts (Facebook Page, Instagram, whatever a Meta Business Portfolio touches), a ticketing or booking platform if you run events, your own website's admin panel if it has one, and — the one people forget — anyone who still has the original login credentials from before you set up proper accounts at all.
That last one matters more than the others combined. A shared password typed into a phone three years ago doesn't show up in any access list, any settings page, any audit. It just sits there, working, until it doesn't. If your business runs on a shared login instead of individual invited accounts, fixing that is step zero, ahead of everything below.
For each surface, write down who currently has access and at what level. Not from memory — actually open each platform's people or team settings and read the list. You will find at least one name you'd forgotten was there. Almost everyone does.
Decide the levels before you decide the people
The mistake I'd been making, and the one I see in almost every small operation with more than one set of hands, is treating access as binary. Either someone's "in" or they're not. Most platforms that manage business accounts offer real gradation, and using it is the entire difference between a manageable system and a liability.
On the Meta side, a person can get full control — post, run ads, manage settings, and add or remove other people, which is functionally the same as owning the account — or a partial role that can post, create events, and answer messages without touching settings or people at all. There's a middle tier that adds ad spend to the partial role for anyone actually running paid campaigns. On a ticketing platform the split usually runs Owner, Admin with full financial visibility, and a custom role that can create and edit events without ever seeing a payout.
The rule that's served me well: default new access to the narrowest role that lets the person do their actual job, and reserve full control for people you'd trust to make a unilateral decision about the account's future, because that is precisely what full control lets them do. A volunteer who posts event flyers needs none of that. A co-owner might need all of it. Most people you'll ever add fall somewhere in between, and the platforms almost always have a tier for exactly where they land — the friction is usually just that nobody stopped to look for it before defaulting everyone to the same level as everyone else.
Full control is not a gesture of trust. It's a decision that this person could, today, remove you from your own Page. Reserve it accordingly.
Granting it — where the interface actively misleads you
Meta's own settings panels have a habit of pointing you at the wrong door, and the wrong door looks entirely plausible until you've walked through it once. From a Page's own asset panel, the button labeled "Assign people" only shows you people already inside your business portfolio — it does nothing for someone new. The actual invite flow, the one that sends an email and works for anyone, lives one level up, under Business Settings → Users → People, not on the Page itself. If you go looking under the Page's own Settings for a way to manage who has access, you'll find a "Manage" link that just bounces you back to the same Business Settings page — a dead end dressed up as a shortcut.
There's a second wrinkle worth knowing before it surprises you: once a portfolio has three or more people with full control, Meta starts requiring a second full-control person to approve certain high-stakes actions. It's a real safeguard, not a bug, but it means the "just give everyone full access so nobody has to ask" instinct actively makes your account slower to operate, not faster. Keep that list short and the friction stays low.
Every invite goes out by email, not by searching a name — have the person's email address in hand before you start, for every one of these systems. The single exception on the Meta side is comment-and-message moderation, which can be assigned by name search alone and needs no email at all, useful if you just need someone answering DMs and nothing more.
Ticketing is a different animal, and the stakes are higher
If your business runs events, whoever has access to your ticketing platform can see — and in the wrong role, touch — actual customer payment flow. Eventbrite splits this more cleanly than Meta does: an Owner role that only one person should ever hold, a full Admin role that reaches everything including payouts, check-in-only roles for door staff on show night, and custom roles you build yourself for people who need to create and edit events but should never see a bank transfer. The custom role is the one almost nobody uses, because building it takes five extra minutes the first time, and it's the one that matters most. A seasonal door person needs check-in. They do not need to see where the money goes, and giving them that access isn't generosity — it's just an unexamined default.
One structural note worth knowing before you build a role: check-in permissions can't be combined with anything else on most platforms. If someone needs to scan tickets and also help with event setup, they need Admin or a custom role built for that combination — there's no middle option that bolts check-in onto a lighter role after the fact.
Run the audit this week, not someday
This doesn't require new software or an afternoon blocked off on a calendar you don't have room in. It requires forty-five minutes, once, and then a habit of maybe two minutes per change after that.
- Open the people or team settings on every platform where your business has a public voice — social, ticketing, your own site's admin panel — and read the actual current list. Not from memory.
- For each name on each list, ask one question: does this person still need to be here, and at this level, today. Not "did they earn it once."
- Downgrade anyone whose role no longer matches their job — the sound engineer who got full access in a hurry eight months ago almost never still needs it.
- Remove anyone who shouldn't be there at all, using the portfolio-level removal above if Meta's connected-asset deadlock shows up.
- Write down what you changed. Who, what level, which system, what date, who approved it. One line each.
Do this once, and the next time takes ten minutes instead of forty-five, because you're maintaining a list instead of reconstructing one from scratch.
Removing it — and the deadlock, when it comes
Here's what actually happened, and the fix, for anyone who lands on this mid-error the way I did.
A Facebook Page and its connected Instagram account are treated as linked assets. Try to remove a person from one while they're still assigned on the other, and Meta refuses, with a message that politely tells you to go remove them from the connected asset first — a message that appears, word for word, on the other platform too, sending you back where you started. It is a genuine loop. You can click both trash icons all afternoon and get nowhere.
The way out is not asset by asset. It's removing the person from the business portfolio itself — the parent container that owns both the Page and the Instagram account. Find their row in the portfolio's people list, open their detail panel, and remove them at that level. One action strips their access to the Page, the Instagram account, and any connected ad account together, because you're revoking the membership the individual asset permissions were hanging off of, rather than fighting each permission one at a time.
One more thing worth knowing before you trust the screen: after a removal, the detail panel doesn't always visually refresh to confirm it worked. A stale-looking panel isn't a failed removal — reload the page before you conclude anything went wrong.
The paper trail is the actual insurance
None of the above holds up without a record, because six months from now you will not remember that you gave the sound engineer partial access in March and upgraded him in June. Every grant, every change, every removal gets one line: who, what level, which system, what date, who approved it. It takes ninety seconds and it is the single cheapest insurance policy available to a business with more than one set of hands touching its public accounts.
When someone new starts, you're not guessing at what they can already reach. When someone leaves, you have an actual list to work from instead of a hopeful memory of "I think that's everyone." And if a customer ever asks who posted something, or a platform ever asks you to prove who had authority to run an ad, you have an answer instead of a shrug.
The volunteer who moved to Bozeman is off every account now, cleanly, and it took about four minutes once I understood the actual mechanism instead of fighting the symptom. What changed wasn't the platform. It was that "who can act as us" went from a question I'd have had to reconstruct under pressure to one I can answer by opening a document. Most owners find out the hard way that their business had more open doors than they knew. Better to count them on a quiet Tuesday than to find out during a departure that isn't as friendly as this one was.
I'm packaging the full version of this system — the access-level decision matrix, the exact invite paths for each platform, a departure checklist, and the log template itself — as The One-Person Business Systems Map, free with your email. It's not live in the vault yet; join the list below and I'll send it the moment it is.
