Contracts provides complete versioned agreements, comparison and two-party
signing. General Group agreements appear at
/portfolio/[groupSlug]/contracts; platform customer agreements have a separate
Commercial control surface. Employment and Event settlement documents retain
People/Ticketing ownership and their own permissions.
Author and issue an agreement
- Open the Agreement library and select New contract.
- Choose its responsible Legal Entity and reference; enter title, each party's legal name/role/signing email, effective date and structured key terms.
- Write the complete Markdown agreement, optionally starting from a published template and inserting reusable clauses. Review the rendered document.
- Save, inspect the complete snapshot and Issue for both signatures.
- Inspect each invitation's delivery state. Retry eligible failed/not-configured delivery through the retained invitation rather than inventing another grant.
Issuing freezes wording, terms, parties, clause versions and document hash.
Template/library updates affect future drafts only. contracts.view reads
permitted general contracts; contracts.manage authors/issues them. Platform,
Employment and settlement authority remain separate.
Recipient reading, signing and amendments
The recipient opens /contracts/[accessId], requests a verification code at the
invited email, verifies it and reads the private frozen document. Codes last ten
minutes with five attempts; the invitation session lasts eight hours. Reading
can remain available after the seven-day signing deadline; signing cannot.
Revocation invalidates the grant on subsequent reads.
What changed compares the issued replacement with the recipient's last signed version, including wording, structured fields, tables and link targets. The recipient consents and signs the exact hash under their verified role. Both required signatures and the effective date are needed before activation.
To amend, select Propose amendment, edit a complete replacement, save and issue it. Only one outstanding amendment exists. The previous agreement remains current until the successor activates. Withdraw proposal removes remaining signing authority while retaining evidence and existing signers' reading access. Stale revisions require reload rather than overwriting concurrent work.
A signed customer commercial agreement does not independently activate platform fees; commercial approval and seller acceptance remain separate. An Event settlement successor does not rewrite an already-approved plan's evidence.