A clear owner for every consent change.

Managed service is enabled for explicitly selected workspaces by authorized staff. Existing workspaces retain their previous permissions until enrollment; a customer owner never becomes platform staff automatically.

• Customer owners and administrators: edit approved appearance fields and business facts, verify a domain, request changes, run permitted scans and import investigation evidence. Only the customer owner manages billing and the ordinary customer team.
• Customer members: read the workspace’s reports, evidence, requests and configuration history. Mutation controls are unavailable.
• Assigned specialists: investigate and classify observations, prepare configuration drafts and record tests. Client access requires an explicit assignment and a staff authenticator verified within the last 30 minutes.
• Assigned publishers: approve and publish a tested draft. The same specialist may prepare and approve a change, but each action is separately recorded. Staff permissions do not grant customer billing or team ownership.

1. 1

   Supply business facts

   Open Sites → your site → Business facts / appearance. Save the legal business name, contact, existing approved privacy/cookie links and declared technologies. These facts are not a generated privacy policy and are not automatically published in the banner.
2. 2

   Prove domain authorization

   Generate the DNS challenge. Add the exact TXT value at the displayed _strongprivacy hostname, then select Verify DNS. Challenges expire after seven days. An installation check-in or Origin header is not domain ownership proof.
3. 3

   Prepare and review the configuration

   Your assigned specialist prepares a candidate and records a test against its exact content hash on an authorized target. A publisher reviews the result and limitations, approves it, then explicitly publishes it.
4. 4

   Install and verify actual behavior

   Use the existing Shopify, WordPress or custom-site installation guide. A newly created managed property does not serve a runtime configuration until ownership and reviewed activation are complete. Previously installed properties retain their last published behavior during enrollment; that compatibility exception is not a new verification result.

Scheduled scans start disabled. Enable them explicitly in the site’s management page after domain verification. The selected plan’s cadence and monthly limits still apply. Manual scans are separate actions, and managed sites also require domain verification before scanning.

The appearance form allows the supported colors, font, position, radius and spacing. Contrast checks run on the server before publication. Customer changes cannot alter categories, required purposes, regional rules, technologies, consent duration or notice copy through this endpoint.

Each appearance publication gets a new display configuration version, while keeping its consent-validity revision. Supported saved choices therefore remain valid for cosmetic changes. Protected changes receive a new consent revision and renew the choice before old optional permissions can be reused. Historical records retain the exact displayed configuration.

If another change was published while your form was open, refresh and reapply your changes. A stale version is rejected instead of overwriting newer work.

1. 1

   Request

   Open Change requests, select the property and describe the desired result. Do not include credentials or visitor information. The request shows the requester, current status, assigned reviewer and attributed history.
2. 2

   Investigate and draft

   A specialist reviews evidence and creates an immutable candidate from the current published version. Investigation links can be attached before approval. A classification review does not silently change a live script.
3. 3

   Test and approve

   Record the test environment, authorized URL, result and limitations for the exact candidate. A failed candidate cannot be approved. A limited result must be explicitly reviewed; it is not a full-site or legal pass.
4. 4

   Publish and verify

   Approval alone is not publication. The publish action rechecks access, ownership, approval, candidate integrity and the current base version together. Record a separate live test after deployment. If changes are requested or the base is stale, prepare a new revision and repeat review.

When the banner and a platform disagree, keep the result unresolved, record the exact configuration and platform settings, and capture the same scenario again. Check duplicate plugins, apps, GTM tags and native tracking separately. Shopify bridge changes are outside this managed-workflow release and require their own acceptance before a Shopify pilot.