OBF token with admin granted scopes

,

Hi Team,

I have a question about using OBF tokens for Meeting SDK apps.

I’ve reviewed the following documents:

  • OBF token transition blog:
    /blog/transition-to-obf-token-meetingsdk-apps/

  • “Get a user’s token” API:
    /docs/api/rest/reference/user/methods/#operation/userToken

From these, my understanding is that a typical pattern is:

  • Each end user authorizes with the granular scope user:read:token, and

  • The app then calls GET /users/me/token?type=onbehalf to obtain an OBF token.

I’d like to confirm a point:

  1. Using admin granular scopes

    If an OAuth app is authorized by an account admin with the granular scope user:read:token:admin, can the resulting access token call
    GET /users/{userId}/token?type=onbehalf
    for arbitrary users in the same account (i.e., obtain OBF tokens on behalf of multiple users without each user completing their own user:read:token consent flow)?
    Or is per-user consent still required in order to issue an OBF token for that specific user?

Any clarification or best-practice guidance for this scenario would be greatly appreciated.

Thanks in advance.