Provision record
Loom · Atlassian Customer Agreement · View original document ↗

Customer settlement requires Atlassian written consent

Common · 224 of 343 platforms
Stay ahead of the changes
Track Loom and hear on the next check after its terms change. We check daily where we can, and show you where we can't.
Share 𝕏 Share in Share 🔒 PDF
ⓘ

This analysis describes what Loom's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

How other platforms handle this

Heap

The Indemnifying Party shall not, without the relevant applicable Indemnified Parties' prior written consent, agree to any settlement on behalf of such Indemnified Parties which includes either the obligation to pay any amounts, or any admissions of liability...

Anyscale

The Indemnifying Party will have the sole right to conduct the defense of any Claim for which the Indemnifying Party is responsible hereunder, provided that the Indemnifying Party may not settle any Claim without the Indemnified Party's prior written approval unless...

Smartsheet

giving the defending party the right to fully control the defense and settlement of the Claim provided, however, that any settlement unconditionally releases Customer Parties or Smartsheet Parties subject to the Claim of all liability...

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
Customer may not settle an Infringement Claim without Atlassian's prior written consent.

Excerpt from Loom's Atlassian Customer Agreement

Provision details

Document information
Document
Atlassian Customer Agreement
Entity
Loom
Tracking information
First captured by ConductAtlas
July 11, 2026
Text quoted from version
CA-V-006808, captured Sept. 11, 2026
Record ID
CA-P-071935
Document ID
CA-D-000564
Evidence Provenance
Source URL
Wayback Machine
Archived bytes SHA-256 (version CA-V-006808)
71fc5e8d24b79e428c9c8b12bb3f49913772ea65ad77685df78205370dd6c899
Analysis generated
July 12, 2026 15:04 UTC
Methodology
Evidence
✓ Excerpt found in version CA-V-006808, captured Sept. 11, 2026 (checked Oct. 5, 2026)
Citation Record
Entity: Loom
Document: Atlassian Customer Agreement
Record ID: CA-P-071935
Version: CA-V-006808
Captured: 2026-09-11 01:02:38 UTC
SHA-256: 71fc5e8d24b79e42…
URL: https://conductatlas.com/platform/loom/atlassian-customer-agreement/provision/CA-P-071935/customer-settlement-requires-atlassian-written-consent/
Accessed: Oct. 24, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Categories

Other risks in this policy

Get the weekly coverage letter

Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.

Frequently Asked Questions

What does Loom's Customer settlement requires Atlassian written consent clause do?

The clause states: “Customer may not settle an Infringement Claim without Atlassian's prior written consent.”

How many platforms have this type of clause?

ConductAtlas has identified this type of provision across 224 platforms. See the full comparison.

Is ConductAtlas affiliated with Loom?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Loom.