Skip to content
AccountMade

Approvals and buyer links

Nothing reaches a buyer unapproved.

Drafts stay internal until your team approves and shares them. Each claim keeps its source, version and approver.

Approve a claim once, with its source.

Each claim has an approver, version and source passage. A claim in review is marked wherever a draft uses it.

  1. Claims5 of 24

    • Data regionv3 · Morgan LeeApproved
    • Encryptionv4 · Morgan LeeApproved
    • Backups and recoveryv2 · Priya ShahNeeds review
    • Access controlv2 · Priya ShahApproved
    • Service levelv2 · Sam RiveraApproved
    1

    Claim status

    Approved, in review or replaced, shown on every claim a draft uses.

  2. Orbiton integrates with Splunk and Datadog for log streaming.Version 1

    Orbiton security whitepaper · Logging and monitoring

    Orbiton streams security logs to Splunk and Datadog on request.

    Approved Sep 2 by Morgan Lee

    2

    Source passage

    Open the excerpt a claim came from, with its page number.

  3. SharedAll links 4

    • Security briefCISO · Pinned link · r21 affected
    • Security review deckDana Weiss · Current link · r3Active
    • Trust roomCISO · Current link · r3Active
    • Data-flow deckCISO · Pinned link · r1Expired
    3

    Buyer links

    Pinned links keep the version you sent. Current links follow what you publish next.

From source to buyer link in four steps.

Rep edits stay as written. A person approves each file before anyone outside your team sees it.

1

Sources and account

Website, security docs, past proposals, call notes and account details.

2

Approved claims

Each has a source passage, a version and an approver.

3

Approval

A person approves the draft before it can be shared or exported.

4

Buyer link or export

A pinned or current link, or DOCX, PPTX, XLSX, HTML or PDF.

Every claim cites its source passage.Orbiton security whitepaper · v1Every code change is peer reviewed and scanned for known security vulnerabilities before release.
Nothing is shared until a person approves it.ApprovedApproved Sep 2 by Morgan Lee
CRM sync is read-only.HubSpotSalesforce
Export every file in the format your buyer opens.DocumentDOCX or PDFDeckPPTX or PDFSpreadsheetXLSX or PDFPageHTML or PDF
Works with the tools your team already uses.Google DriveMicrosoft 365HubSpotSalesforceSlack

See the source next to the sentence.

Open any claim in a draft to see its source passage, version and approver. Rep edits stay as written.

  • A claim in review is marked wherever it is used.
  • Rep edits stay as written when a claim changes.
Linked claim
Selected text

Halden Freight’s shipment records are encrypted in transit and at rest.

ClaimVersion 4

Orbiton encrypts customer data in transit and at rest and keeps encryption keys in AWS KMS.

Status · Approved by Morgan Lee

Approved Sep 24, 2026

Supporting excerpt
Customer data is encrypted in transit with TLS 1.2 or higher and at rest with AES-256. Encryption keys are held in AWS KMS.
Orbiton security whitepaper

Choose what the buyer sees: pinned or current.

A pinned link keeps the version you sent. A current link follows what you publish next. Every export comes from the approved version.

  • Each claim keeps its source and approver.
  • A person approves each file before it can be shared.
Buyer linkHalden Freight security brief
PinnedFixed to what you approvedCurrentFollows your latest approved files

Expires · 30 days

ActivityHalden Freight
  1. Link createdSam RiveraOct 3, 10:02
  2. Sent by emailCISOOct 3, 10:03
  3. OpenedCISOOct 3, 14:40
  4. QuestionCISO · Data residencyOct 3, 14:52
  5. Answer approvedMorgan LeeOct 4, 09:15
  6. Opened by a forwarded viewerDana WeissOct 4, 11:30
  7. Read to the endDana WeissOct 4, 11:48

When a reviewer asks where a sentence came from, open the claim: source passage, version, approver.

3 linked claims · 1 source

Related pages

Common questions

Where does a claim in a draft come from?

From a source you added: a website page, security document, past proposal or call note. A person approves the claim, and it keeps the excerpt, version and approver.

What if we have no approved claim for a question?

The requirement shows as a gap or needs a document. Write the answer by hand, ask the owner to add a source and approve it, then share.

Can we see who approved what?

Yes. Each claim records its approver, version and date, and the activity feed shows who approved each file and when.

Stop rewriting the same answers.