LinkedIn Marketing API OAuth scope boundaries for Ad Account management

Ad Account Permission Hierarchy

When integrating a third-party application with the LinkedIn Marketing Developer Platform, the rw_ads scope provides the necessary write access for managing sponsored updates. However, the API enforces a strict hierarchy where the application's capabilities are bounded by the authenticated user's specific role within the LinkedIn Campaign Manager.

Configuration Uncertainty

In scenarios where an application must manage multiple ad accounts across different organizational structures, it is unclear how the API handles token validation when a user's role is downgraded or removed from a specific Ad Account while an active OAuth 2.0 access token remains valid.

• Does the API perform a real-time permission check against the Campaign Manager role for every request?
• What is the expected behavior when a token with rw_ads scope attempts to modify an entity for which the user no longer holds the required administrative role?