Google: YouTube scopes submitted for verification

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
metatroncubeswdev 2026-10-22 19:41:13 -04:00
parent 5b5a14411f
commit 482cf4253e

View File

@ -53,6 +53,9 @@ Two Google Cloud projects, both owned by dev@metatroncubesolutions.com:
together with the demo video link):
> Quorla (quorlasocial.com) is a social media management tool for marketing agencies. An agency admin connects a client's YouTube channel on Quorla's Connections page. youtube.upload: the team prepares a video post in Quorla; an admin reviews and approves the exact video, title, description, visibility and made-for-kids setting, and Quorla uploads it to the connected channel at the scheduled time. Nothing is uploaded without that approval. youtube.readonly: show which channel is connected (name, handle, avatar, subscriber count) so the agency posts to the right channel, and link to the uploaded video afterwards. More limited scopes are not sufficient: youtube.upload is the narrowest scope that allows uploading, and youtube.readonly is needed to read the channel identity, which upload alone does not return. Tokens are encrypted at rest and deleted when the channel is disconnected.
Status 22 Oct 2026 (evening): **Quorla project submitted for verification** (youtube.upload, youtube.readonly) with demo
video https://youtu.be/lB8FMGDbBOo (unlisted); Data access status "under review". Google replies by email to dev@.
Status 22 Oct 2026: GMB Audit (Business Profile) is **done**: In production, branding verified and published, and
"Verification is not required" for data access (business.manage is non-sensitive). Home page https://quorlasocial.com.
Any Google account can now connect Business Profile; reconnect connections made while it was in Testing once, so