Publishing workflow
The tool uploads KarmSakha-created lessons, updates titles and descriptions, sets thumbnails, attaches caption tracks, manages playlist membership and checks processing status.
Google OAuth verification
YouTube API reviewer access
This is the official reviewer entry point for KarmSakha Content Uploader, an owner-operated tool used only to publish KarmSakha educational videos to the official KarmSakha YouTube channel.
Application overview
What the integration does
Private-first safety
New uploads are private by default. A human operator checks the finished video, captions, thumbnail and metadata before scheduling or changing visibility.
Single-channel gate
Every write is restricted to official channel ID UCBDDvNEJP2snShGu-Smwxog. A channel mismatch stops the operation.
Exact navigation
How a Google reviewer reaches the consent screen
The app has no public customer sign-in and no KarmSakha password. Testing uses an authorised Google reviewer account in a supervised, preconfigured local environment.
Open the reviewer entry point
Start on this public page and open the unlisted end-to-end demonstration linked below.
Use the supervised test environment
The uploader is an owner-operated local command-line application, not a public web login. Contact [email protected] if the Google reviewer account or a supervised test session has not yet been supplied.
Start Google authorisation
The operator starts the uploader's OAuth command. It opens Google's consent flow in an English-language browser and returns to a loopback address on the same computer after consent.
Use the Google reviewer account
Choose the Google account supplied by the verification team. The OAuth app is External and in production, so the Console has no test-user allowlist. For a channel-backed write test, KarmSakha must authorise the exact reviewer email for a supervised session. No separate KarmSakha username or password exists.
Review and grant the two scopes
The consent screen requests only YouTube upload access and YouTube account-management access. Granting consent creates a protected local token for the authorised test session.
Verify the channel safety gate
Before any write, the uploader calls YouTube channels.list and requires the official KarmSakha channel ID. A different channel ends the run without uploading or changing content.
Exercise the private-first workflow
An approved operator can upload a KarmSakha-owned video privately, set its metadata and thumbnail, add captions and playlist membership, and verify processing. Public scheduling happens only after human review.
Requested permissions
OAuth scopes used
YouTube upload
https://www.googleapis.com/auth/youtube.uploadUsed to upload KarmSakha-owned educational videos.
YouTube account management
https://www.googleapis.com/auth/youtube.force-sslUsed for metadata, thumbnails, captions, playlists, comments, visibility and post-upload verification on the authorised channel.
Reviewer support and disclosures
Access, privacy and revocation
The OAuth app is External and in production, so Google Auth Platform does not expose a test-user allowlist. KarmSakha will authorise the exact Google reviewer email for a supervised channel test when Google supplies it. If no reviewer address was supplied, email [email protected]with the address. KarmSakha will never share the channel owner's password or two-factor authentication credentials.