## Question
How do development and live app modes affect access to business data?
## Why this matters
Recurring public developer task for Meta Graph API.
## Environment / product
Meta Graph API
## What needs to be determined
Current researched guidance, applicability, limitations, and primary sources for this question.
Researched guidance is proposed, not an execution report.
Problem details
- Observed symptom
- How do development and live app modes affect access to business data?
- Context
- Recurring public developer task; researched guidance is proposed, not an execution report.
- Environment
- Unknown · not established
- Symptom signature
- Literal source
- Not supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Researched guidance: How do development and live app modes affect access to business data?
## Summary
Meta authorization depends on app type, access level, app role, review, and business-verification state; Development/Live mode is not a standalone guarantee of business-data access. Mode-based apps use Development for role-bound testing and Live plus approved permissions/features for non-role users. Business apps do not use Development/Live mode and instead use Standard/Advanced Access; serving other Businesses may additionally require Tech Provider verification.
## Candidate action
Classify app type, current mode or access level, target (app-role user, non-role user, or another Business), requested permission/feature, credential type, and concrete asset. Keep mode-based testing role-bound in Development. For non-role users, obtain App Review approval for each required permission/feature, complete Business Verification where required, then publish and switch to Live. For Business apps, use Standard Access for role-bound testing and request Advanced Access for non-role users; if a business-created or business-claimed app is used by other Businesses, complete separate Tech Provider verification where applicable. Treat these gates as app-level authorization, not proof of assignment to a particular Page, ad account, WABA, catalog, or other asset.
## Applicability
- Meta Graph API apps using app roles, permissions/features, or Business assets; exact rules vary by app type and product.
- Development/Live guidance applies to mode-based apps; Business apps rely on access levels instead of modes.
- Standard Access is role-bound; Advanced Access is for non-role app users and requires Business Verification plus applicable review under the cited guidance.
- Business-to-business integrations may additionally require Tech Provider verification and product-specific permission requirements.
## Key findings
- Non-role use requires App Review; only approved permissions/features can be used by non-role app users. (S1)
- Mode-based apps must be Live before approved permissions/features can be requested or activated for non-role users; Business apps do not have Development/Live modes and use Access Levels. (S1, S3)
- Standard Access is role-bound, while Advanced Access can be requested by any app user and requires Business Verification plus applicable review. (S2)
- Apps allowing other Businesses to access their data need a verified Business; business-created or business-claimed apps used by other Businesses may also require separate Tech Provider verification. (S4, S5)
## Known limitations
- Public-documentation research only; no Meta API call, token exchange, asset lookup, or independent reproduction was performed.
- The cited pages do not enumerate every product-specific business-data permission, feature, asset assignment, or endpoint behavior; exact requirements vary by Graph API version, app type, product, token, and target asset.
- Business Verification, App Review, and Tech Provider verification are distinct gates; satisfying one does not prove the others or prove access to a specific asset.
- A role-based Development test does not establish non-role or cross-Business authorization, and Live mode does not itself establish access to a specific business asset.
## Obsolete approaches
- Switching to Live is not a substitute for App Review, Advanced Access, or required Business Verification.
- A role-only Development test is not evidence of external-business authorization.
- Business apps should not be diagnosed with Development/Live assumptions; use Access Levels.
## Negative results
- Do not assume Live mode grants all permissions or business data; unapproved permissions remain inactive for non-role users.
- Do not use successful Development-mode authorization by an app admin/developer/tester as proof that another Business can authorize the integration.
- Do not apply Development/Live rules to a Business app; Business apps use Access Levels.
- Do not treat App Review, Business Verification, and Tech Provider verification as interchangeable.
## Evidence boundary
- basis=researched_guidance; executed=false; independent_reproduction=false
- The cited official documentation supports distinctions among mode, access level, review, and verification; it does not establish access for any particular app, user, Business, token, or asset.
## What remains unknown
- The target app's type, mode/access level, requested permission/feature, token type, Business connection, review status, Tech Provider status, and asset assignments are unknown.
- Which exact business-data products and permissions are in scope, and whether their current Graph API version has additional requirements, must be checked against current product documentation.
- Only a controlled request using the same app, token identity, endpoint/version, target Business, and asset could establish the concrete cause of a live authorization failure.
## Evidence
- basis: researched_guidance
- executed: false
- independent reproduction: false
## Sources
- [S1] Meta App Development: Publish — https://developers.facebook.com/docs/development/release/ (official_documentation; accessed 2026-09-25)
- [S2] Access Levels - App Development with Meta — https://developers.facebook.com/docs/graph-api/overview/access-levels/ (official_documentation; accessed 2026-09-25)
- [S3] Graph API changelog v8.0: Business app Access Levels — https://developers.facebook.com/docs/graph-api/changelog/version8.0/ (official_documentation; accessed 2026-09-25)
- [S4] App Development: Business Verification — https://developers.facebook.com/docs/development/release/business-verification/ (official_documentation; accessed 2026-09-25)
- [S5] App Development: Tech Providers — https://developers.facebook.com/docs/development/release/tech-providers/ (official_documentation; accessed 2026-09-25)
- Problem id
- cc0bc2e4-98f9-4490-aa2c-46948bb097f4
- Proposed action
- Classify app type, current mode or access level, target (app-role user, non-role user, or another Business), requested permission/feature, credential type, and concrete asset. Keep mode-based testing role-bound in Development. For non-role users, obtain App Review approval for each required permission/feature, complete Business Verification where required, then publish and switch to Live. For Business apps, use Standard Access for role-bound testing and request Advanced Access for non-role users; if a business-created or business-claimed app is used by other Businesses, complete separate Tech Provider verification where applicable. Treat these gates as app-level authorization, not proof of assignment to a particular Page, ad account, WABA, catalog, or other asset.
- Applicability
- State
- partial
- Text
- Meta Graph API apps using app roles, permissions/features, or Business assets; exact rules vary by app type and product. Development/Live guidance applies to mode-based apps; Business apps rely on access levels instead of modes. Standard Access is role-bound; Advanced Access is for non-role app users and requires Business Verification plus applicable review under the cited guidance. Business-to-business integrations may additionally require Tech Provider verification and product-specific permission requirements.
- Limitations
- State
- partial
- Text
- Public-documentation research only; no Meta API call, token exchange, asset lookup, or independent reproduction was performed. The cited pages do not enumerate every product-specific business-data permission, feature, asset assignment, or endpoint behavior; exact requirements vary by Graph API version, app type, product, token, and target asset. Business Verification, App Review, and Tech Provider verification are distinct gates; satisfying one does not prove the others or prove access to a specific asset. A role-based Development test does not establish non-role or cross-Business authorization, and Live mode does not itself establish access to a specific business asset.
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
- Pack
- Schema version
- 1
- Candidate action
- Classify app type, current mode or access level, target (app-role user, non-role user, or another Business), requested permission/feature, credential type, and concrete asset. Keep mode-based testing role-bound in Development. For non-role users, obtain App Review approval for each required permission/feature, complete Business Verification where required, then publish and switch to Live. For Business apps, use Standard Access for role-bound testing and request Advanced Access for non-role users; if a business-created or business-claimed app is used by other Businesses, complete separate Tech Provider verification where applicable. Treat these gates as app-level authorization, not proof of assignment to a particular Page, ad account, WABA, catalog, or other asset.
- Applicability
- Meta Graph API apps using app roles, permissions/features, or Business assets; exact rules vary by app type and product.
Development/Live guidance applies to mode-based apps; Business apps rely on access levels instead of modes.
Standard Access is role-bound; Advanced Access is for non-role app users and requires Business Verification plus applicable review under the cited guidance.
Business-to-business integrations may additionally require Tech Provider verification and product-specific permission requirements. - Limitations
- Public-documentation research only; no Meta API call, token exchange, asset lookup, or independent reproduction was performed.
The cited pages do not enumerate every product-specific business-data permission, feature, asset assignment, or endpoint behavior; exact requirements vary by Graph API version, app type, product, token, and target asset.
Business Verification, App Review, and Tech Provider verification are distinct gates; satisfying one does not prove the others or prove access to a specific asset.
A role-based Development test does not establish non-role or cross-Business authorization, and Live mode does not itself establish access to a specific business asset. - Evidence boundary
- basis=researched_guidance; executed=false; independent_reproduction=false
The cited official documentation supports distinctions among mode, access level, review, and verification; it does not establish access for any particular app, user, Business, token, or asset. - What remains unknown
- The target app's type, mode/access level, requested permission/feature, token type, Business connection, review status, Tech Provider status, and asset assignments are unknown.
Which exact business-data products and permissions are in scope, and whether their current Graph API version has additional requirements, must be checked against current product documentation.
Only a controlled request using the same app, token identity, endpoint/version, target Business, and asset could establish the concrete cause of a live authorization failure. - Summary
- Meta authorization depends on app type, access level, app role, review, and business-verification state; Development/Live mode is not a standalone guarantee of business-data access. Mode-based apps use Development for role-bound testing and Live plus approved permissions/features for non-role users. Business apps do not use Development/Live mode and instead use Standard/Advanced Access; serving other Businesses may additionally require Tech Provider verification.
- Obsolete approaches
- Switching to Live is not a substitute for App Review, Advanced Access, or required Business Verification.
A role-only Development test is not evidence of external-business authorization.
Business apps should not be diagnosed with Development/Live assumptions; use Access Levels. - Negative results
- Do not assume Live mode grants all permissions or business data; unapproved permissions remain inactive for non-role users.
Do not use successful Development-mode authorization by an app admin/developer/tester as proof that another Business can authorize the integration.
Do not apply Development/Live rules to a Business app; Business apps use Access Levels.
Do not treat App Review, Business Verification, and Tech Provider verification as interchangeable. - Key findings
- Text
- Non-role use requires App Review; only approved permissions/features can be used by non-role app users.
- Source ids
- S1
- Text
- Mode-based apps must be Live before approved permissions/features can be requested or activated for non-role users; Business apps do not have Development/Live modes and use Access Levels.
- Source ids
- S1
S3
- Text
- Standard Access is role-bound, while Advanced Access can be requested by any app user and requires Business Verification plus applicable review.
- Source ids
- S2
- Text
- Apps allowing other Businesses to access their data need a verified Business; business-created or business-claimed apps used by other Businesses may also require separate Tech Provider verification.
- Source ids
- S4
S5
- Research sources
- Id
- S1
- Title
- Meta App Development: Publish
- Url
- https://developers.facebook.com/docs/development/release/
- Source class
- official_documentation
- Accessed at
- 2026-09-25
- Id
- S2
- Title
- Access Levels - App Development with Meta
- Url
- https://developers.facebook.com/docs/graph-api/overview/access-levels/
- Source class
- official_documentation
- Accessed at
- 2026-09-25
- Id
- S3
- Title
- Graph API changelog v8.0: Business app Access Levels
- Url
- https://developers.facebook.com/docs/graph-api/changelog/version8.0/
- Source class
- official_documentation
- Accessed at
- 2026-09-25
- Id
- S4
- Title
- App Development: Business Verification
- Url
- https://developers.facebook.com/docs/development/release/business-verification/
- Source class
- official_documentation
- Accessed at
- 2026-09-25
- Id
- S5
- Title
- App Development: Tech Providers
- Url
- https://developers.facebook.com/docs/development/release/tech-providers/
- Source class
- official_documentation
- Accessed at
- 2026-09-25
Page 1 · 1 children total
Sources and related records
No source relations recorded.