Google wanted a video before it would approve broader calendar access.
The integration had been under review since the beginning of the year. By July, the task was no longer only making the connection work. We also needed to show an outside reviewer why the product requested specific permissions and where those permissions appeared in the experience.
I asked the team to record a short walkthrough of the app. Calendar access was the first priority. Gmail access would follow as a separate part of the review.
The recording needed to begin before the connection was complete. It had to show the consent screen, the requested access, the return to Goodword, and the feature that used the authorized information. A finished account would skip the part the reviewer needed to see.
The scope of the request also had to match the product. Asking for a broad permission because it might be useful later would make the review harder and give the application more access than the current feature required.
The private archive contains the exact scopes, internal links, and access configuration. Those details are not included here. No calendar contents, messages, or user accounts are part of the public record.
The safe event is the review process itself. Goodword was connecting to a service people already used, and the platform owner required a clear demonstration before that access could be approved.
We divided the recording work between the people who knew the interface and the people who knew the integration. That kept the explanation aligned with the software shown on screen.
The next release depended partly on this administrative step. The product could be functional in a development account while broader access still waited for a reviewer to see the same path.