First-Party Signatures

Agreements signed inside CloudMonkey.

CloudMonkey will operate its own signature workflow for customer agreements. Quotes, service orders, MSAs, DPAs, AI addendums, and immediate provisioning consent can be accepted without a third-party signing provider.

Signature Workflow

A first-party audit trail for each agreement

The goal is to make the accepted document, signer authority, timestamp, acceptance wording, and evidence bundle visible from the dashboard.

Prepare

CloudMonkey generates the quote, MSA, service order, DPA, SLA, AI addendum, and any provisioning consent from the current catalog and customer scope.

Accept

The authorised signer reviews the document in the dashboard, confirms authority, accepts the required policies, and signs without leaving CloudMonkey.

Record

The platform stores the document hash, signature metadata, version, consent text, and immutable document snapshot for later audit and dispute handling.

Provision

Provisioning starts only when payment, required consents, service scope, and signature status meet the product's onboarding rules.

Audit Evidence

What the platform should preserve

A signature is only useful if the evidence survives later commercial, security, and compliance disputes.

Signer account ID, name, email address, and organisation.

Timestamp, IP address, browser user agent, and source route in the dashboard.

Document type, document version, quote ID, service order ID, and customer account ID.

Clear acceptance wording shown at the time of signature.

SHA-256 hash of the accepted document snapshot.

Immutable HTML or PDF snapshot retained with the agreement record.

Checkboxes for MSA, DPA, AI addendum, service scope, immediate provisioning consent, and recurring billing authority where applicable.

Admin-visible history showing who prepared, sent, viewed, accepted, superseded, or voided the document.

No third-party signature dependency

CloudMonkey can still export signed documents for customer records, but the acceptance event, evidence bundle, document hash, and signed state remain in CloudMonkey's own database and admin dashboard.