Can the “reason” field for Zoom Marketplace app requests be made mandatory, and what intake information do others collect? | Community
Skip to main content
R
Newcomer
Renee Jones
Newcomer
April 1, 2026
Question

Can the “reason” field for Zoom Marketplace app requests be made mandatory, and what intake information do others collect?

  • April 1, 2026
  • 1 reply
  • 60 views

Hi everyone, I’m exploring governance and intake processes for Zoom Marketplace app requests in an enterprise university environment.
 

At present, when a user clicks Request to Add for a Marketplace app, the request email we receive only contains very limited information such as:

  • requestor name

  • requestor email

  • app name

 

There is also an optional reason field in the Zoom request pop-up, but in practice this is often skipped, and we are also finding that it may not reliably carry through into our downstream ticketing workflow.

I wanted to ask whether anyone in the Zoom Community has dealt with similar issues and, if so, how you approached them.

 

I would like to know:

  1. Can the “reason” field on a Zoom Marketplace app request be made mandatory?
  2. Has anyone successfully passed that field into ServiceNow or another ticketing system?
  3. What minimum fields do you collect before deciding whether to review an app request?
  4. Do you use a second intake form or triage form to gather purpose, users, cost, accessibility, privacy, and security details?

 

Any advice or examples from higher education or enterprise settings would be appreciated.

Thanks.

    1 reply

    ExpertswhoJohn
    Community Super Champion | Customer
    ExpertswhoJohn
    Community Super Champion | Customer
    April 1, 2026

    hi ​@Renee Jones ,

    Happy to discuss this in more details. 

    Let me explain how the marketplace works from the developer side first.

    When a developer wants to wrtie an app, they need to specific to Zoom all the function calls that they would like access to in order for their app to run. Zoom ONLY gives them access to what they request and will check the reasons before they allow the developer to release their app on the marketplace.
    When you go into the marketplace as a user or admin, you see an approval screen which allows you to see the summary of the information they will be accessing.

    I am not sure of your use case. Are you looking to put apps in the marketplace, or to use them.

    If you give a user the right to make apps for the marketplace they can register apps in developer mode, must specifcy the fiunctions needed, but in the devleoper mode is not monitored by zoom.

    If you are looking at using marketplace apps for use in your account, then you can lock down the access and only allow apps that you approve and then make them available to the user base.

    For more support we have a seprate forum and also “office hours” session every two weeks. I am one of the community developers and also attend that session.

    Zoom has a separate forum for developers. You will get much faster response there where Zoom engineers are available.
    devforum.zoom.us

    Please like and mark as the solution if this helps

    All the best

     

    John Drinkwater

    Zoom Community Super Champion.

    Zoom Developer Champion

    Community Champions are not paid to provide this support and have no access to customer settings or data. I am not personally an employee of Zoom

    https://www.linkedin.com/in/johndrinkwaterlordzoom/
    See my latest content. events, live and prerecorded to showcase features
    https://lordzoom.com/go/hub
    I run many events and upload most on my channel.
    https://www.youtube.com/@boomwithlordzoom
     

    R
    Newcomer
    Renee JonesAuthor
    Newcomer
    April 9, 2026

    Hi John,

    Thanks for the reply. To clarify, I am asking from the customer/admin governance side rather than the developer side.

    Im not looking to publish apps to the Zoom Marketplace. Im looking at the process where an end user in our institution selects Request to Add for an existing Marketplace app, and that request is then sent to the Zoom account admin for review.

    My questions are specifically about that request workflow:

    1. Is there any way to make the reason field mandatory when a user submits a Request to Add request?
    2. Can that reason field be reliably passed through in the notification or downstream workflow?
    3. Is there any supported way to collect additional intake information at the point of request, such as:
      • intended use case
      • expected users
      • cost implications
      • accessibility considerations
      • privacy/security considerations

    At the moment, the notification we receive only gives us very limited information, which makes governance and triage difficult.

    If this is not configurable in the standard Marketplace request flow, can you confirm that plainly? That would still be helpful.

    If this question is better suited to the developer forum or office hours, Im happy to post it there, but I wanted to first check whether anyone knew the answer from the admin side.


    Thanks
    Renee

    ExpertswhoJohn
    Community Super Champion | Customer
    ExpertswhoJohn
    Community Super Champion | Customer
    April 9, 2026

    hi ​@Renee Jones ,

    I am an independent developer for Zoom and a Zoom Developer Champion. So I do know this process well. We have an developers office hours every two weeks if you would like to discuss this.

    I have contacts who run large corporate and educational accounts and they have an internal process for the user to request access to an app and asking the sort of questions you give. They have a starting position of not enabling any apps till they approve. For privacy reasons, I suggest you should collect that information yourself.

    As far as knowing what the app does, the developer process requires them to declare exactly what zoom data they want access to and only those functions are then allowed in their app.
    This means zoom can give a clear indication of the privacy and compliance of all apps. The scopes are the key for the data accessed, so using Notion as an example as random. It has access to user data and meeting data. I would agree that you may want a software expert to give an opinion for your organisation.

     

    all the best

     

    John

    Terms & ConditionsAccessibility statement
    Copyright © Zoom Communications, Inc. All rights reserved.