Skip to content

Update from code changes: Automated Takedowns legal authority prompt - #205

Open
mintlify[bot] wants to merge 3 commits into
mainfrom
mintlify/108f32b6
Open

mintlify[bot] wants to merge 3 commits into
mainfrom
mintlify/108f32b6

Conversation

@mintlify

@mintlify mintlify Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Updates the Automated Takedowns docs to reflect that the service can be enabled without legal authority on file, with takedowns held in Pending Input until a document is added, and that brand-level websites and LoA/POA documents now count.

Changes

  • Replace the "cannot be enabled" warning with a description of the legal authority modal (Go to Legal Documents / Later) and Pending Input behavior
  • Accept LoA, POA, or takedown authorization. The enable prompt checks organization-level documents only. Releasing a held takedown also accepts an LoA or POA on the takedown's brand when that brand uses its own documents
  • A website URL on the organization or on one of its brands satisfies the website requirement
  • Update the prerequisites table and fix the upload path to Settings → Legal Documents

Context

  • chainpatrol/chainpatrol-web#9001: Prompt for an LoA or takedown authorization when enabling Automated Takedowns
  • chainpatrol/chainpatrol-web#9782, #9780, #9711: Accept LoA or POA everywhere, and count brand websites and brand LoA/POA

Update history

  • Initial PR: documented the legal authority modal, Pending Input, accepted document types, and the Legal Documents path (#9001)
  • Website URL can now be on the organization or a brand. Clarified that brand-level LoA/POA count when releasing held takedowns, while the enable prompt checks organization-level documents only (#9782, #9780, #9711)

Note

Low Risk
Documentation-only changes with no runtime or security behavior in this repo.

Overview
Updates Automated Takedowns setup docs to match the product change where the service can be turned on before legal authority exists, instead of blocking enablement until a POA and org website URL are present.

The Requirements warning now describes the Go to Legal Documents / Later modal, Pending Input queueing for takedowns that still need LoA or takedown authorization, and automatic release after upload—including brand-level LoA/POA when a brand uses its own documents. Prerequisites and required-docs lists broaden POA-only language to LoA, POA, or takedown authorization, and allow a website URL on the organization or a brand. The service documentation table and upload tip point users to Settings → Legal Documents and clarify docs are needed before takedowns can be submitted, not necessarily before toggling the service on.

Reviewed by Cursor Bugbot for commit 6a1b023. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
chainpatrol 🟢 Ready View Preview Nov 5, 2026, 1:10 PM

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved. Cursor Bugbot completed successfully with no findings that need human review, and this is a documentation-only update to Automated Takedowns setup guidance.

Open in Web View Automation 

Sent by Cursor Approval Agent: Pull Request Router

@mintlify

mintlify Bot commented Nov 5, 2026

Copy link
Copy Markdown
Contributor Author

Update from code changes updated this PR.

Automated Takedowns now accept a website URL, LoA, or POA on a brand, not only the organization.

Source PRs

This branch was successfully deployed

1 active deployment
staging — 6a1b023f Deployed Nov 5, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants