> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lynkacrm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Documentation changelog

> Track meaningful changes to the Lynka public documentation structure, product explanations, workflow coverage, LeadGen guidance, Teams guidance, and search-focused help content.

This page tracks changes to the **public documentation**, not every change to the Lynka application.

Use the application release notes or product communication channels for feature releases. Use this changelog when the help center changes enough that a reader, support person, or search engine should understand the new structure.

## August 2026: workflow-first documentation rebuild

The documentation was reorganized around the work entrepreneurs and small teams are trying to finish rather than treating each product area as an isolated feature list.

Major changes include:

* Lead Generator became a first-class documentation section with targeting, run lifecycle, CRM handoff, credits, refunds, team use, measurement, privacy, troubleshooting, and FAQ guidance.
* Teams became a first-class product story with small-team examples, assignment, manager visibility, product access, action permissions, record scope, approvals, and member offboarding.
* The homepage now starts with practical goals such as finding customers, closing sales, quoting and invoicing, managing stock, understanding finances, and running a team.
* Financial reporting was expanded into separate guides for Trial Balance, General Ledger, Profit & Loss, Balance Sheet, Cash Flow, A/R Aging, A/P Aging, account balances, and bank reconciliation readiness.
* Regional setup guidance was added for businesses across Africa, Europe, and the Middle East, covering currency, FX, tax configuration, timezone, and privacy responsibility.
* Search metadata and internal linking were rewritten around real user questions rather than generic feature names.

## Editorial rule

The documentation should describe what Lynka actually does, explain the business meaning before the UI when necessary, and avoid inventing provider behavior, legal compliance, pricing, or plan limits that are not verified.