Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.adclear.ai/llms.txt

Use this file to discover all available pages before exploring further.

Overview

Controlled workflow

Self-approval is available only to explicitly permitted users, on explicitly permitted promotions. It is not a blanket permission.

Not a global rule

Adclear does not enforce a platform-wide block on all uploader-reviewer overlap. Organisations requiring strict separation should support this with a governance process.
Self-approval is designed for a narrow use case where an organisation has determined that certain users can review their own uploaded promotions under controlled conditions. It is not available by default and does not apply to all promotions or all reviewers.
This page covers the current operational mechanics of self-approval. For the broader direction Adclear is taking on automated approvals — including what may become available longer-term under controlled rollout — see the Self-Approvals entry in the Features Guide.

How It Works

All of the following conditions must be satisfied for a self-approval to proceed.
Self-approval must be enabled at the organisation level. Without this, the workflow is unavailable to all users regardless of their individual permissions.
The user must be explicitly marked as a self-approver. A standard uploader cannot access this workflow unless that permission has been specifically granted.
The self-approver must also hold review permission for the relevant country or market. Self-approver status does not override jurisdiction restrictions.
The Self Approval toggle must be enabled on the specific promotion. If it is not, the self-approver flow is unavailable for that promotion regardless of user permissions.
The self-approver must be the uploader of that promotion. Self-approver permission cannot be used to review another user’s promotion.
AI review must have completed before self-approval can proceed. If AI evaluation is still running or has not started, the self-approver is blocked from reviewing.
If AI review completes and there are unresolved AI comments, the self-approver cannot proceed until those comments have been responded to. See Helping Adclear Learn for guidance on responding to AI comments effectively.

Platform Restrictions

When the self-approver workflow is active, Adclear enforces the following hard restrictions.
RestrictionWhat it means
Self-approver role requiredOnly users explicitly configured as self-approvers can use this workflow
Jurisdiction permission still appliesThe self-approver must hold review permission for the relevant market
Own uploads onlyA self-approver can only review a promotion they uploaded themselves

Segregation of Duties

The self-approver workflow restrictions apply specifically to the dedicated self-approver path. Adclear does not enforce a universal, platform-wide block across all approval paths.
This means there is no code-level guarantee that uploader and reviewer can never be the same person in every workflow. Reviewer assignment alone should not be treated as a complete segregation-of-duties control. Organisations whose internal policy or regulatory framework requires strict separation between creator and approver should treat this as a governance consideration and support it with a monitoring process — not rely on the self-approval toggle alone.

Operational Controls

The following is a practical baseline. It is not prescriptive — teams should adapt it to their risk appetite, regulatory context, and operating model.
1

Restrict access to grant self-approver status

Access to grant self-approver status and to enable promotion-level self-approval should sit with a restricted group — such as compliance, operations, or platform administration — rather than general marketing users.
2

Run a regular uploader-reviewer check

A periodic review of cases where the uploader and reviewer are the same person provides a practical safeguard. This can be run as a saved report or export at a set cadence, covering both the self-approver path and the standard review path.
3

Review exceptions

Where uploader and reviewer match, confirm the case was expected under policy and appropriately authorised. Spot-checking approved content on an exception basis adds a further assurance layer.
4

Document the control

Record the control owner, review cadence, and the steps to follow if a case falls outside policy. This supports consistent governance and provides an audit trail.
A simple saved report filtered by “uploader = reviewer” reviewed at a fixed interval — monthly or quarterly depending on volume — is often sufficient as a baseline control.

Quick Reference



Still need help?

Contact support

Reach the Adclear support team directly.

Back to overview

Return to the Adclear documentation home.