How to Offboard a System User on Facebook the Right Way
System users carry access of their own, and removing one cleanly takes more than deleting a person.
Is this your situation?
You are preparing to retire a system user, the account that lets servers or software call your business assets, and want to remove it without breaking anything else. A clean offboarding separates what the system user touched from who else still depends on the same access.
Where teams go wrong
- Assuming one token covers everything A separate system user should be created for each type of access needed.Why it happens: Teams reuse one system user for several integrations.
- Removing without checking admin status An admin system user can create system users.Why it happens: You remove it without checking what it manages.
- Treating tokens as reusable A system user token can only be shared once.Why it happens: Teams expect to retrieve an old token again after offboarding.
- Not re-securing the admin token The admin system user token should be carefully safeguarded because it has the most permissions.Why it happens: Old tokens are not rotated after someone leaves.
What good practice looks like
| Practice | What good practice looks like | What weak practice looks like |
|---|---|---|
| System user scope | A separate system user is created for each type of access needed. | Not stated by Facebook |
| Admin system user use | Use of the admin system user is limited to administrative actions such as assigning permission. | Not stated by Facebook |
| Regular system user reach | Regular system users can only access the assets they have permission for. | Not stated by Facebook |
| Token handling | Each new system user requires a new generated token. | Not stated by Facebook |
How Facebook handles this
- System users represent servers or software that make API calls to assets owned or managed by a business portfolio.
- An admin system user can create system users.
- Regular system users can only access the assets they have permission for.
- Not all businesses have access to system users.
- A business portfolio cannot be deleted if it has system users.
Before you start
- Confirm which type of system user you are removing An admin system user can create system users.Verify: Check whether this system user is the admin type before removing it.
- Check what the system user can reach Regular system users can only access the assets they have permission for.Verify: Review the assigned assets list for this system user.
- Check whether system users exist at all Not all businesses have access to system users.Verify: Look in System users under the Users tab.
- Check portfolio deletion dependency A business portfolio cannot be deleted if it has system users.Verify: Check the portfolio's system user list before any deletion plan.
Which scenario is yours?
- Is the system user the admin type? An admin system user can create system users, so confirm no other process depends on it.
- Does the system user hold access to several assets? Regular system users can only access the assets they have permission for, so each asset's dependency can be checked individually.
- Will you need this access again later? A system user token can only be shared once, so a replacement would need a newly generated token.
Keeping this working over time
- A separate system user for each type of access needed keeps offboarding contained to one function.
- Use of the admin system user limited to administrative actions such as assigning permission reduces what a single removal affects.
- Review your current system users against who still holds access before removing any one of them.
If control is already lost — Recover a Hacked Facebook Business Portfolio
Keeping track of who has access
Delvia keeps a record of who and what holds access across people and systems, not only at the moment of removal. A system user is one more identity sharing your business assets, and it needs the same visibility as any person. Clear records make an offboarding a planned step rather than a guess about what else depends on it. That structure is what keeps access changes legible over time.
Was this helpful?