RTMS Enablement for Published Marketplace Apps in Multi Tenant Environments

I had a question regarding RTMS behavior for published Marketplace apps using the Meetings SDK.

If an app is published on the Zoom Marketplace and uses RTMS features, does each Zoom organization/account installing the app also need to separately enable RTMS on their own tenant/account side?

Or does RTMS access automatically work for all organizations once the Marketplace app itself has RTMS enabled and approved?

Trying to better understand how RTMS provisioning works in a multi-tenant Marketplace app environment.

Yeah - each Zoom organization/account installing the app should have RTMS enabled or allowed on its own tenant/account side. Marketplace publication and app approval make the app eligible to use RTMS, but they do not appear to replace the customer tenant’s own admin controls. Zoom describes RTMS as something account admins can enable at the account, group, or user level.

So for a multi-tenant Marketplace app, treat this as two layers: your app must be configured with the right RTMS features and scopes, and each installing tenant must allow real-time meeting content sharing for apps through their Zoom admin settings. A published app being RTMS-approved does not prove RTMS will work for every customer account that installs it.

We’re a Zoom RTMS Preferred Partner, if you want someone to manage your RTMS integration for you.

I have a question, what is the different on “RTMS enabled” and “allowed on its own tenant/account side” ?
Thank you.