> ## Documentation Index
> Fetch the complete documentation index at: https://docs.korint.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Comments & internal notes
> How teams annotate policies, customers, and other records with public comments and firm-scoped internal notes without altering transactional history.
Teams need somewhere to coordinate and leave context alongside a policy or a customer — a reminder of what was agreed on a call, a note explaining why an exception was granted, a hand-off between colleagues. Korint provides annotations for exactly this. They live next to the record without ever touching the contract or its transactional history, so you get a working audit trail without risk to the underlying data.
Two kinds of annotation exist, differing in what they can be attached to and who can see them.
***
## Public comments
Public comments can be attached to **any entity** in the platform — a policy, a customer, an asset, an invoice, and so on. They are the general-purpose way to leave a note on a record that the team working on it can read.
* Create, edit, and delete comments on a record.
* List all comments attached to a given entity, so the full thread of context is visible in one place.
***
## Internal notes
Internal notes are **broker-internal annotations on policies**. They exist for context a firm wants to keep to itself rather than share broadly.
Internal notes are **visibility-scoped to the firm**. Every broker in the author's brokerage firm can see them; a user who does not belong to that firm sees no internal notes at all — they are never exposed on the public comments surface.
Like comments, internal notes support create, edit, and delete, and a listing view per policy. The difference is entirely in reach: comments are for the team working the record, internal notes are for the firm that owns it.
A note belongs to the policy rather than to a specific quote, so it stays visible after the policy is signed, through amendments, and even if the quote it referred to is later archived. Each note shows its author's name and business role together with its creation and last-edit times. Only the author can edit or delete their own note—not even an administrator can change someone else's—and a deleted note is hidden from everyone but retained internally for audit (permanent removal can be requested from Korint for data-privacy compliance). Notes are plain text, up to 5,000 characters each, with no limit on the number per policy.
***
## Comments versus internal notes
Attach to **any entity** — policies, customers, assets, invoices, and more. Visible to the team working the record.
Attach to **policies** only. Firm-scoped — visible solely to brokers of the author's firm.
***
## Why annotate
The business value is coordination and traceability without side effects:
* **Coordination** — colleagues leave context for one another directly on the record they are working, instead of in a separate tool that drifts out of sync.
* **Audit trail** — annotations sit alongside the policy or customer as a durable record of what was discussed and decided.
* **No impact on the contract** — because annotations are separate from the transactional history, adding, editing, or removing them never alters the policy, the billing, or any other part of the contract itself.