Phase E · Easy Cloudflare enforcement
Install the ContentDividend Worker without editing Worker code.
Choose your website, provide a narrowly scoped Cloudflare API token, and ContentDividend can install the E2 authorization Worker in Observe Only. Your API token is used for this request and is never stored in the ContentDividend database.
No rights are created here. E3 only installs the edge messenger. Agreements, payment, activation, publisher authorization, credentials, RSL/OLP and exact-resource rights stay exactly where they already live.
What E3 automates
1. Worker uploadContentDividend uploads the current Worker to your Cloudflare account.
2. Secure bridge bindingA separate private deployment credential is placed into the Worker as a Cloudflare secret.
3. Route creationThe Worker is attached to the selected website route only when there is no conflicting route.
Before you click Install
Create a Cloudflare API Token, not your Global API Key. Give it only the permissions E3 needs:
- Account → Workers Scripts → Edit
- Zone → Workers Routes → Read + Edit
- Zone → Zone → Read so ContentDividend can confirm the Zone matches your registered website.
ContentDividend does not save the token. It is sent to Cloudflare during this install request and then discarded. If you prefer not to provide a Cloudflare token to ContentDividend at all, use the normal Cloudflare Authorization page and the Deploy-to-Cloudflare/manual package path instead.
Install in Observe Only
Loading your websites…
Safety rules built into E3
- E3 refuses to overwrite an existing Cloudflare Worker route for the same host pattern.
- The first deployment stays in ContentDividend Observe Only; E3 does not silently switch on enforcement.
- The Cloudflare API token is not stored.
- The Worker receives a separate deployment secret, not your Cloudflare API token.
- If ContentDividend authorization is unavailable, the E2 Worker continues its existing fail-open reference behavior.