A Meta system user is a non-human identity inside your business portfolio that represents a server or piece of software rather than a person. You assign it ad accounts, Pages, datasets and catalogs, install your Meta app on it and generate an access token, so reporting pipelines, automated rules, bulk launchers and Conversions API servers keep running when people join or leave. Meta's documentation allows one admin system user per business, plus one regular system user on the default Limited tier of Marketing API access or ten on Full access. This guide covers when a person's token fits better, setup, token expiry, partner-shared ad accounts, rate limits and API versions.
What a system user is, and when a person's token is better
Meta defines a system user as a server or software that calls its APIs on assets owned or managed by a business portfolio, the current name for Business Manager. It is created in Meta Business Suite settings and holds asset assignments the way a person does, but it never logs in: it authenticates with a system user access token generated for a Meta app. Meta's authentication guide positions these tokens for server-to-server work with no user present, notes they need not expire and says they are less likely to be invalidated than long-lived user tokens.
That makes a system user the right identity for anything that runs unattended: an hourly Insights pull into a dashboard, an automated rules engine, a bulk launcher fed from a queue, a catalog sync or a server sending conversion events. The token belongs to the business rather than to anyone's profile, so it keeps working when the employee who built the integration leaves, loses access or changes their password, the moments when integrations built on personal tokens break.
A person's own token is the better choice when a human acts in real time. Meta's system users documentation warns that if you use a system user token to act for a real person, you cannot associate that person with those actions, and it recommends that people who manage ad accounts complete Meta's standard OAuth flow and use their own user access token. Meta's business login documentation adds that user tokens are needed for APIs that require admin permissions on a business portfolio. A launcher where buyers press publish should log each buyer in rather than share one system token.
Admin vs regular system users, and how many you can have
Meta has two kinds. An admin system user can create other system users, create ad accounts and assign permissions, and by default it has full access to every asset owned by or shared with the business portfolio. A regular system user, created with the Employee role, can only access the assets it has been assigned. Meta advises keeping the admin system user for control tasks such as creating system users and assigning access, never for day-to-day asset work, and creating one regular system user per type of access you need, so a compromised token exposes as little as possible.
How many you get depends on your app's Marketing API Access Tier. On May 4, 2026 Meta renamed Ads Management Standard Access to Marketing API Access Tier, with Standard Access becoming Limited access and Advanced Access becoming Full access. Meta's authorization page says Limited access, granted automatically when you add the Marketing API product, allows one system user and one admin system user, while Full access, approved through App Review, allows ten system users and still one admin system user. Older pages, including parts of Meta's own system user and rate-limit documentation, still use the Standard and Advanced names for the same two tiers.
To qualify for Full access, Meta currently asks for at least 500 Marketing API calls in the past 15 days with an error rate below 15% across the last 500 calls; you request it with Upgrade on the Marketing API Access Tier feature in the App Review area of the App Dashboard. Two prerequisites come first: a real person must be an admin of the business, and an app must be part of the business before any system user can be created. Meta's help center also notes that not every business has access to system users. Hitting a cap returns error 3949 for system users or 3965 for the admin system user.
Creating a system user and assigning ad accounts, Pages, datasets and catalogs
The quickest route is the interface. Meta's access token documentation describes it in Business settings, now the Settings area of Meta Business Suite, and the checklist at the end of this section follows that order; Meta's help center labels a few buttons differently.
Each asset type has its own task set. In the API, ad accounts take MANAGE, ADVERTISE and ANALYZE, which map roughly to the old admin, advertiser and analyst roles, and Pages add tasks such as CREATE_CONTENT and MODERATE. A reporting job needs only ANALYZE, a launcher ADVERTISE plus ANALYZE, and very little automation needs MANAGE. Datasets are assigned to a system user in business settings, which is how Meta's Conversions API instructions attach a pixel to one, and catalogs take system users through their own assigned users edge.
At scale, script the assignments. A POST to an ad account's assigned users edge with the system user's app-scoped ID, the task list and your business ID grants access, using an admin's or the admin system user's token, and reading the system user's assigned ad accounts confirms the result. Meta warns to use the app-scoped ID the API returns, not the ID shown in the interface. Conversions API tokens are the exception: Meta recommends generating them for each dataset in Events Manager, where its setup flow creates a dedicated Conversions API app and system user for you. Our Conversions API setup guide covers that flow.
- Open Settings, then Users, then System users, and click Add
- Enter a name and choose the Admin or Employee role
- Assign your app with the Manage app permission so the system user has full control of it
- Assign the ad accounts, Pages, datasets and catalogs the integration needs, with the narrowest tasks that work
- Click Generate token, select the app, choose an expiration and tick only the permissions you need
- Copy the token at once: Meta shows it only once, and a lost token means generating a new one
Generating tokens: permissions, expiry and safe storage
Permissions decide what a token can do on the assets its system user holds. Meta's permissions reference says ads_read gives access to the Ads Insights API for reporting and also covers sending server events through the Conversions API; ads_management reads and manages ads on accounts you own or have been granted; business_management reads and writes through the Business Manager API, such as managing assets. A dashboard needs ads_read, a launcher ads_management, and only tooling that manages assets or assigns access needs business_management.
Expiry is chosen at generation. A non-expiring token never needs refreshing. An expiring token is valid for 60 days from creation or its last refresh. Meta's developer documentation recommends expiring tokens as a security best practice that limits the damage of a leak, says some businesses must use them and says all integrations should adopt them. An expiring token that is not refreshed in time is lost and has to be regenerated, so schedule the refresh through the token exchange endpoint well before day 60. If you still pick never, pair it with tighter storage and a tested revocation routine.
Treat every token like a production password. Meta's guidance is to keep tokens in secure, encrypted storage, move them only over HTTPS, request the minimum scope, check validity regularly and sign server-to-server calls with appsecret_proof, a hash of the token keyed with your app secret. The Access Token Debugger shows a token's app, expiry and scopes. Keep tokens out of code repositories, shared sheets and chat, give each environment its own token, and record which system user and app every token belongs to.
System users on partner-shared ad accounts
Many high-spend teams run on agency ad accounts that another business portfolio owns and shares into theirs through partner access. Meta's documentation supports system users on those accounts: employee system users can be granted assets owned by, or shared with, your business portfolio, and Meta's system user permissions guide covers these proxied assets, which a system user can call the API on for the tasks it has been given. The system user, the app and the token all live in your own portfolio.
The owner sets the ceiling. Meta's partner-sharing help says a business with partial access to a shared asset can only assign people in its own portfolio the specific tasks it was given, and even full control does not let a partner re-share the asset with another business. In the API, the tasks that can be assigned on an account appear in its permitted_tasks field. If a launcher needs ADVERTISE on an account shared for reporting only, the fix is a sharing change by the owner, not a new token.
Two habits keep this clean. An employee system user does not pick up newly shared accounts, while the admin system user does by default, so script the assignment with the admin system user and every newly shared account reaches the right integrations on day one. Then keep one map of account ID, owning business, tasks granted and system users assigned, because a removed share breaks API calls just as surely as a revoked token.
This is how Power Ads works with teams spending roughly $100k or more a month on Meta. Accounts are created in our business portfolio, run on our corporate cards and are shared into your Business Manager through partner access once you send your Business Manager ID or an admin invite link. Your system users, apps, tokens and integrations stay with your team: we supply the accounts, with no cap on how many and free replacements, and do not build or run integrations or campaigns. Pricing is 4% deducted from each top-up, with no setup or per-account fee.
Marketing API rate limits at multi-account scale
The Marketing API has its own rate limiting, and most of it is counted per ad account. Your app's tier sets the quota: Meta describes Limited access as heavily rate limited and meant for development, not for production apps serving live advertisers, and Full access as lightly rate limited. Business use case limits are computed per ad account for each use case, such as ads management, Insights and custom audiences, and the first two grow with the account's active ads. They are not per user, so adding system users adds no quota.
Response headers on rate-limited endpoints tell you where you stand. The X-Business-Use-Case-Usage header reports, per ad account, the percentage of call count, CPU time and total time used, plus an estimated time to regain access once throttled; X-Ad-Account-Usage gives the account's utilization and time to reset; and X-FB-Ads-Insights-Throttle covers Insights calls at app and account level. Log them whenever they appear and slow down well before 100%, instead of waiting for throttling errors such as codes 17, 613 or the 80000 series.
Some limits matter directly for automation. Meta's rate-limiting page currently lists 100 create or edit requests per second per app and ad account for campaigns, ad sets and ads, one edit to the same object every 30 seconds by default, four budget changes per ad set per hour and ten changes to an ad account's spending limit per day. Insights also has app-level limits that throttle every account at once. Spread jobs over time, batch reads, use asynchronous Insights jobs for large pulls and back off exponentially when throttled.
Page size is a separate question. On an edge such as an ad account's ads, the limit parameter is only an upper bound on objects per page; Meta says some edges cap it for performance and does not publish one universal maximum, so request pages of a sensible size and follow the next link until it disappears.
API versions and breaking changes: keeping integrations alive
Every Marketing API call names a version, and Meta says unversioned calls fail. A new version ships roughly every four months, and Meta keeps the previous one available for at least 90 days after its successor ships; in practice recent versions have lasted about a year. As of mid-November 2026, the changelog lists v27.0, introduced November 4, as current and v26.0, introduced July 29, with no end date yet; v25.0 is available until February 23, 2027, and v24.0, introduced October 8, 2025, reached its end date on November 10, 2026.
End dates are not the only risk. Meta's changelog says versioned changes typically apply to the newest version first and often extend to older versions later, while out-of-cycle changes usually hit all versions at once. Our news post on Meta's 27 October breaking changes covers a recent case: several changes launched with v26.0 on July 29 reached every version 90 days later, so tools pinned to older versions were not protected. Some v27.0 changes are already marked to apply to all versions about 90 days after launch.
Since May 2024, Meta auto-upgrades calls to an expired version on endpoints that did not change and adds an X-Ad-Api-Version-Warning header to the response; calls to endpoints that did change still fail. Treat that header as an alarm, not a safety net. Keep the version in one config value, log the warning header, read each changelog when a version ships, run a test launch and a reporting pull on the new version, and upgrade well before the end date.
Least privilege, token rotation and offboarding tools
Build access around jobs, not people. Within your tier's cap of one regular system user on Limited access or ten on Full, give each integration or access type its own, with the narrowest tasks and permissions that work: a reporting user with ANALYZE and ads_read, a launcher with ADVERTISE, ANALYZE and ads_management, and Conversions API tokens per dataset from Events Manager. Keep the admin system user's token for assigning access and creating system users, store it apart from everything else and use it rarely. When a token leaks, only one job is exposed.
Rotate on a schedule. For expiring tokens Meta documents a zero-downtime pattern: refresh the token, which issues a new one valid for 60 days while the old one keeps working until it expires, switch the integration to the new token, then revoke the old one, which takes effect immediately. Rotate at once after a suspected leak, a vendor change or the departure of anyone who could see a token.
For offboarding, Meta's revoke endpoint kills a single token, and one DELETE call to a system user's access tokens edge invalidates every token it holds. Meta's developer documentation says system users and admin system users cannot be deleted, so retiring one means revoking its tokens and unassigning its assets. Third-party tools connected through Facebook Login for Business are removed under Integrations, then Connected apps, in business settings. Review system users and their assets monthly alongside people access, which our guides to Business Manager roles and permissions and to team access and roles in agency setups cover.
Key takeaways
- A Meta system user is a non-human identity in your business portfolio for unattended, server-to-server API work; for people acting in real time, Meta recommends their own OAuth user token.
- Meta allows one admin system user per business plus one regular system user on Limited access, or ten on Full access, of the Marketing API Access Tier.
- Within that cap, give each integration or access type its own regular system user with the narrowest tasks and permissions, and keep the admin system user for assigning access.
- Prefer 60-day expiring tokens with a scheduled refresh, which Meta says all integrations should adopt, store tokens encrypted and sign server calls with appsecret_proof.
- On partner-shared ad accounts, your system users can only receive the tasks the owning business granted to yours.
- Rate limits are mostly counted per ad account and set by your app's tier, and breaking changes can reach every API version, so watch usage headers and the changelog.
FAQ
What is a system user in Meta Business Suite?
A system user is an identity in your business portfolio that represents a server or software rather than a person. You assign it ad accounts, Pages, datasets or catalogs and generate an access token for a Meta app, so automated tools can call the Marketing API without anyone logging in. Because it belongs to the business, its token keeps working when staff change.
What is the difference between an admin system user and a system user?
An admin system user can create other system users, create ad accounts and assign permissions, and by default it can access every asset owned by or shared with the business. A regular system user, created with the Employee role, only reaches the assets assigned to it. Meta allows one admin system user per business and recommends using it only for control tasks.
How do I create a system user in Meta Business Manager?
In Meta Business Suite, open Settings, then Users, then System users, click Add, name it and choose the Admin or Employee role. Assign your app with the Manage app permission, then the ad accounts, Pages, datasets or catalogs it needs. Click Generate token, pick the app, an expiration and the permissions, and copy the token, which Meta shows only once. An app must be part of your business first.
Do Meta system user access tokens expire?
It depends on the option you pick when generating one: a token that never expires, or an expiring token valid for 60 days from creation or its last refresh. Meta recommends expiring tokens because they limit the damage of a leak, says all integrations should adopt them, and some businesses must use them. Refresh them through the token exchange endpoint before day 60, or the token is lost and must be regenerated.
Can I assign a partner-shared ad account to my own system user?
Yes. Meta's documentation says employee system users can be granted assets owned by, or shared with, your business portfolio, and the admin system user can access shared assets by default. You can only assign the tasks your business received from the owner; with partial access, that means only those specific tasks. If an integration needs more, the owning business has to change the share.
What are the Meta Marketing API rate limits?
There is no single number. Meta counts most limits per ad account, sets the quota by your app's Marketing API Access Tier and grows the ads management and Insights quotas with active ads. Specific caps include 100 create or edit requests per second per app and ad account, one edit per object every 30 seconds by default and four budget changes per ad set per hour. Usage headers such as X-Business-Use-Case-Usage show how close you are.
Sources
- developers.facebook.com/docs/marketing-api/system-users
- developers.facebook.com/docs/marketing-api/system-users/overview
- developers.facebook.com/docs/marketing-api/system-users/create-retrieve-update
- developers.facebook.com/docs/marketing-api/system-users/install-apps-and-generate-tokens
- developers.facebook.com/docs/marketing-api/system-users/guides/permissions
- developers.facebook.com/documentation/ads-commerce/marketing-api/get-started/authorization
- developers.facebook.com/documentation/ads-commerce/marketing-api/get-started/authentication
- developers.meta.com/blog/updates-to-ads-management-standard-access-feature
- developers.facebook.com/documentation/ads-commerce/marketing-api/reference/business/system_users
- developers.facebook.com/documentation/ads-commerce/marketing-api/reference/business/client_ad_accounts
- developers.facebook.com/documentation/ads-commerce/marketing-api/reference/ad-account/assigned_users
- developers.facebook.com/documentation/ads-commerce/marketing-api/reference/product-catalog/assigned_users
- developers.facebook.com/documentation/facebook-login/guides/access-tokens
- developers.facebook.com/documentation/facebook-login/facebook-login-for-business
- developers.facebook.com/documentation/facebook-login/security
- developers.facebook.com/documentation/ads-commerce/conversions-api/get-started
- developers.facebook.com/docs/permissions
- developers.facebook.com/documentation/ads-commerce/marketing-api/overview/rate-limiting
- developers.facebook.com/docs/graph-api/overview/rate-limiting
- developers.facebook.com/docs/graph-api/results
- developers.facebook.com/documentation/ads-commerce/marketing-api/overview/versioning
- developers.facebook.com/documentation/ads-commerce/marketing-api/marketing-api-changelog
- developers.facebook.com/documentation/ads-commerce/marketing-api/marketing-api-changelog/version26.0
- developers.facebook.com/documentation/ads-commerce/marketing-api/marketing-api-changelog/version27.0
- facebook.com/business/help/1717412048538897
- facebook.com/business/help/503306463479099
- facebook.com/business/help/327596604689624
