App Review: Domain testing constraint & guidance request for "Momentum by Salesforce"

App Marketplace App Submission
1

Hi Team,

We’re kicking off the app review/approval process for “Momentum by Salesforce” and wanted to raise an important constraint up front, along with a question for you.

Why we’re raising this now: the domain constraint described below (production vs. our pre-production environment) isn’t something we’ve hit before, so we don’t have a clear read on how long it might take to resolve or work around. We’re posting this early and proactively — before it becomes a blocker in the review — so we can get your guidance ahead of time rather than discovering it mid-review.

App under review
App name: Momentum by Salesforce
Client ID: jkaZhW0zRjKa3h8hq_rzcA

The constraint

We understand unpublished (development/beta) apps are restricted to users within the developer’s own Zoom account. Our pre-production Salesforce environment runs on a separate internal domain — a different domain/account context than our production environment — so we’re unable to pair the production app’s development client with our pre-production environment for the reviewer walkthrough.

As a workaround, the walkthrough we’re providing for review uses the development client of a separate Marketplace app (Client ID: pzJ0g0SVTj2FaGwOu4JlmQ) against our pre-production org instead. This substitute client is only a stand-in for the demo — the scopes and behavior it shows are representative of, and directly justify, what’s requested by the production app under review. Flagging this explicitly so it isn’t mistaken for the actual app being approved.

Our question for you

Because of the restriction above, we can’t simply add your reviewer’s Zoom account to our workspace the way we could for a Google account. What’s the recommended way for your review team to test an unpublished/development app outside the developer’s own account? We want to get this sorted before it holds up the review.

We already have an approved app “Momentum” (Client ID: 5UMFYXzeRQ2McB_HTlqdJQ), and the new “Momentum by Salesforce” app does exactly what the approved app does. We are basically rebuilding same functionality again using a new app.

Happy to answer any questions.

Thanks,
Vishnu Rekapalli

2

Hello, your post alittle confusing, you mentioned testing a development app, but we usually test new submissions using the production client and update requests using the development client ID.

If you cannot provide access to your test environment, we can complete testing over a meeting. In this meeting, when the page for Zoom Authorization pops up, we will fill in our Zoom credentials, and we can use the meeting to verify all functionality.

Regards, Kwaku

3

Hi Kwaku,

Thanks for the quick response!

To clarify: our production client isn’t deployed yet, so we have to use the Development Client ID (jkaZhW0zRjKa3h8hq_rzcA) for testing.

The constraint we’re hitting is Zoom’s policy that restricts unpublished dev clients to users within our own Zoom account. Because you can’t install our dev client directly from your reviewer account, we would love to take you up on the live testing meeting.

Please share a booking link or your availability so we can set up the call, demonstrate the app in action, and have you complete the OAuth step on the spot.

Thanks,
Vishnu

4

I’ll monitor this thread while my colleague Vishnu is past his working hours. Hoping we can schedule a live walkthrough soon to showcase the app and how we use the scopes.

Thanks,
Johannes