I’m looking for some insight into the private app publishing; I’ve been writing an internal-only app for our Zoom environment to integrate with intranet services, and have ran into some issues with the publishing flow.
The “Authorization URL FAQ” guide suggests the “Beta”/“Unpublished” authorization URL expires with limited extensions, however, a “Published” app does not. I would like clarification on if we can trust the “Users within my account” published state as it stands for my app to not expire for our users.
Under the marketplace when editing the app, it shows a green “Published” in the bottom left next to “Publish your app”, and under the “Visibility” section, it shows “Users within my account - Live”. However, it still has the “Beta” tag on the right side on both the unlisted marketplace entry when clicking “View My App Details” on the panel in the top right, and the “Beta” tag in the banner of the header inside the Zoom Workplace client when opening my app.
I’ve read through all the publishing documentation, along with several articles on here to try and determine what the “Beta” tag means in relation to the authorization URL and its expiry; it seems like it may not be truly published internally for us. It’s also not cached, I have used several browsers and new Workplace clients to no avail. Any information would be appreciated, thank you!
Thank you for raising this question. The best approach depends on your specific use case.
If you are looking for a long-term solution to allow users outside your account to use your app while maintaining control over distribution, please review the following documentation and follow the steps that best fit your app’s needs:
I have no interest in allowing users outside of our account to access the app. It’s meant to be an unlisted/private app only meant for users inside of our organization.
Thank you for the clarification. If that is the case, users within your account can already add the app without your app needing to be approved in App Review. If you’d like the app to be reviewed and approved so that it is ‘published’, you can set the app’s discoverability as unlisted, but you do need to go through the App Review process.
Hi Yoon, yes we are able to distribute it internally within our organization as expected, that’s not an issue after I added it for the “Everyone” option, which is great. It’s not necessarily that I want it to be “Published” specifically, however, what I’m wondering is that after reading the guide “Authorization URL FAQ”, I noticed the authorization URL expires with limited extensions.
With a private/internal app, I’m wondering if this would still be the case, and the fact that the “Beta” tag is still showing up in the client/marketplace even though it’s published, does that still mean the app will expire for users in our organization? Under the “Publish” tab at the bottom, it says “Users within my account - Live” with a green “Published” pill next to the menu. I can provide screenshots if that would be easier, however, it won’t let me add them to the post.
In short, I’m just trying to figure out if the app will eventually expire for our users unless I make it a public app with the official review process; and if so, what we can do to prevent that. Thanks!