The audit log is a chronological record of everything that has ever happened to your cap table. Every time a stakeholder is added, a security is issued, a document is merged, an approval is granted, or tokens are minted, Launchboard writes an immutable event to the log. You can use the audit log to answer questions like “when was this grant issued?”, “who approved this?”, and “what document authorized this change?” — quickly and without hunting through email threads or spreadsheets. Navigate to Governance → Audit Log (Documentation Index
Fetch the complete documentation index at: https://docs.launchboard.xyz/llms.txt
Use this file to discover all available pages before exploring further.
/audit-log) to view the full history.
What the audit log shows
Each event in the log includes:- Timestamp — when the event occurred, in your local timezone
- Event type — what kind of change happened (issuance, governance, document, tokenization, stakeholder change)
- Description — a plain-English summary of the action
- Actor — the user or system process that triggered the event
- Provenance link — a link to the source document in the Dataroom, where applicable
Event types
| Event type | Examples |
|---|---|
| Security issuance | New stock certificate issued, SAFE recorded, option grant created |
| Stakeholder change | Stakeholder added, wallet address updated |
| Document merge | Extraction applied to cap table from a Dataroom document |
| Governance | Approval submitted, approval step approved, approval locked |
| Token mint | Tokens minted on-chain, transaction hash recorded |
Provenance links
Every ledger event that originates from a document carries a link back to that document. Click any event with a provenance link to open the source document in the Dataroom — you can see the original PDF, the extracted data, and the seal hash if the document was signed. This is Launchboard’s bi-directional audit trail: every cap table state change traces back to the document that authorized it.No orphan events
Every event in the Launchboard audit log has a documented source — either a Dataroom document (with its own extracted data and optional seal hash) or an explicit user action. There are no “orphan” events: you can always answer the question “where did this come from?” This invariant is maintained automatically. When you merge a document, the resulting cap table records carry the document’s ID. When you issue securities manually, the actor and timestamp are recorded. When tokens are minted, the on-chain transaction hash is stored on the security and referenced in the log.Using the audit log for due diligence
Investors and legal reviewers often ask for a complete history of cap table changes before a financing round or acquisition. The audit log gives you that history in one place.Open the audit log
Go to Governance → Audit Log. You will see the full event history for your cap table.
Filter by date range
Use the date filter to narrow the log to a specific period — for example, all events since your last financing round.
Filter by event type or stakeholder
Filter by event type (e.g., show only issuances and governance events) or by a specific stakeholder to produce a focused history.
Related pages
Board actions
Create and manage approval requests that authorize cap table changes.
Cap table reports
Generate ownership summaries and dilution analyses for investor meetings.
Dataroom overview
Learn how documents are stored, extracted, and linked to cap table records.