I’m currently reviewing several part of our app submission and while the required content of the documentation URL page is pretty clear so far, whether it must be a public page, or whether we can protect it with an account access is not defined.
The Zoom app we are trying to submit will anyway require an authentication to our services and the same authentication will permit to view the given page.
Can the documentation page be protected behind own services authentication?
It depends we can make an exception for that but you would need to provide reasoning for why it needs to be configured that way. Please provide us a Login where we can review the documentation URL and confirm it meets our standards too. If that cannot be be provided you can also provide a PDF of the page so we can review it too.
Please remember documentation URLs musts contain the following
Since our app will only be accessed by our users who have existing accounts (similar to Yohann’s above point on authentication above), can we provide some of these documents as Google Docs please?
For our clients who will use this, they get a copy of these documents when they sign up to services with us, but these are not public documents. I assume we could be informed of the tester from Zoom that we need to grant access to these documents for?
You can provide it as a Google doc in the release notes but not in the documentation URL slot; please provide something else there because doing so will cause issues with domain validation. Also, please explain everything in the release notes that is not left for your development. If you can also provide login credentials we can use to inspect the documentation URL, that would be enough.