Question 1
What business problem does ContentBridge CMS solve?
It turns owned YouTube content into structured website CMS entities so teams can publish video libraries, collection pages, and embed blocks without repetitive manual entry.
Frequently Asked Questions
FAQs for ContentBridge CMS
Practical answers covering OAuth scope use, manual sync operations, and v1 data-handling limits.
Question 2
Why is youtube.readonly required?
The scope is required to read your owned channel, playlists, and uploaded video metadata so the app can build website-ready structures.
Question 3
Does the app modify anything on YouTube?
No. The product is read-only and does not provide upload, edit, delete, or channel-settings controls.
Question 4
How does sync work in v1?
v1 is manual-sync only. You run sync when you want a new snapshot from YouTube; no scheduled sync is included in this release.
Question 5
Is data stored permanently in this release?
No. Workspace state is session-only in v1 and clears on refresh or sign-out.
Question 6
How is workspace data handled in this release?
Workspace data is kept for the active authenticated session and is refreshed from source data whenever sync runs.
Question 7
How do I disconnect access?
Use the Disconnect action inside the CMS workspace. The app attempts token revocation and signs you out.