What Is a System User in Meta Business
A system user is a credential for software, not a person, and it works differently from the roles you give people.
Is this your situation?
You have come across the term "system user" while setting up access in Meta Business Suite and are not sure what it is. You want to know whether it behaves like a person's account or like something else.
What it is
System users represent servers or software that make API calls to assets owned or managed by a business portfolio. There are 2 types of system users. An admin system user can create system users. Regular system users can only access the assets they have permission for. Not all accounts have access to system users.
How Facebook handles this
- A separate system user should be created for each type of access needed.
- System users should be given access to assets and used for most API calls.
- The admin system user should be used to maintain the right roles programmatically.
- Use of the admin system user should be limited to administrative actions such as assigning permission.
- A system user token can only be shared once.
Side by side
| Aspect | Admin system user | Regular system user |
|---|---|---|
| Create system users | Can create system users. | Not stated by Facebook |
| Access scope | Can assign permissions. | Can only access assets it has permission for. |
| Permission level | Has the most permissions among system users. | Not stated by Facebook |
| Token handling | Token should be carefully safeguarded because it has the most permissions. | Each new system user requires a new generated token. |
Common mistakes
- Using the admin system user for routine API calls Use of the admin system user should be limited to administrative actions such as assigning permission.Why it happens: The admin system user has the most permissions among system users.
- Sharing one system user across several integrations A separate system user should be created for each type of access needed.Why it happens: Each new system user requires a new generated token.
- Losing a token after it is issued A system user token can only be shared once.Why it happens: After generating a token, the token must be copied and saved.Already happened: If you are not sure who still holds system user access, review auditing access.
Quick reference
| Term | What it means |
|---|---|
| System user | Represents servers or software making API calls to business portfolio assets. |
| Admin system user | Can create system users. |
| Regular system user | Can only access assets it has permission for. |
| System user types | There are 2 types. |
| Access by account | Not all accounts have access to system users. |
| Token sharing | A system user token can only be shared once. |
| New system user | Each new system user requires a new generated token. |
Frequently asked questions
Is a system user the same as a person's account?
A system user represents servers or software that make API calls to assets owned or managed by a business portfolio.
What can an admin system user do that a regular one cannot?
An admin system user can create system users, while a regular system user can only access assets it has permission for.
Can I reuse a token for another system user?
Each new system user requires a new generated token.
Does every account have system users available?
Not all accounts have access to system users.
Keeping track of who has access
Confusion about who and what holds access often builds quietly as more system users and tokens get added over time. Delvia gives you a clear view of every system user and person with access, so nothing stays unclear.
Was this helpful?