Approvals and Oversight
Who this is for
Section titled “Who this is for”Founders and senior decision-makers who have the relevant module access. Availability of an action still depends on the assigned permission matrix.
Review the source record
Section titled “Review the source record”- Invoices and commissions: use the finance record to see current amount, status, payment, balance, and report details before an approval or paid status is recorded.
- Contracts: use the contract record to see the current signing state. A forced signed state is intentionally confirmed because it bypasses provider-status verification.
- Campaign and delivery commitments: use the campaign and creator execution records; do not infer delivery from a dashboard card alone.
Before approving
Section titled “Before approving”- Confirm that the financial, legal, or operating evidence is present on the underlying record.
- Confirm the actor has the relevant manage permission where a management action is needed.
- Treat an integration shown as configured separately from one that has completed a live provider verification.
What happens next
Section titled “What happens next”Approvals and configuration changes should be traceable through the relevant record and, for admin operations, the Audit log. The audit trail records after the primary operation succeeds; it does not make the original operation transactional.