Use case: org documentation
Documentation projects go stale the week they finish. Let the org explain itself, save the answers that matter, and let the history record itself.
In one paragraph
Documenting a Salesforce org with SyncOnAI 360 means using the synced repository as the living reference, asking the chat to explain components and saving useful answers as pages, recording meetings as transcripts, keeping runbooks beside the org, and relying on change history and receipts for what changed and why.
01The problem
Documentation is written once, by someone with a deadline, about an org that keeps changing. Within months it describes a different org.
Nobody updates it after the project ends.
It lives in a wiki nobody connects to Salesforce.
Why something was built is never written down.
Documenting everything is a project nobody funds.
02living
The synced repository: every object, field, Flow, class and component with full source, refreshed every six hours and after deploys. Search it from the Knowledge Hub, and open any component into its lineage.
For what exists and how it connects, the org is the documentation, and it never goes stale.
03explain
Ask the chat to explain a process, an object's automation or a class, and save the answer as a page with one click. The Flow builder explains each Flow in plain sentences, and the Architecture lens profiles how the org is built.
04why
Record calls into transcripts saved as pages, and keep requirements, decisions and runbooks beside the org and project. Pages are searchable and cited by the AI in its answers.
05history
The Changes lens records what changed and when; every deploy through SyncOnAI 360 has a receipt with the request behind it, the checks and the approver. That history writes itself.
06share
Share health and audit reports as read-only links; pages stay inside the workspace. Claude and Cursor can read the org itself through the read-only MCP connection.
07start
With the processes people ask about most. Ask the chat to explain each one, check the answer against the org, and save it as a page. A handful of well-chosen pages answers most questions, and the repository covers the rest.
Add runbooks for the jobs that are done rarely and done under pressure, such as a release or a rollback.
08How it works
Start small and let it accumulate.
The repository becomes the reference.
Ask about key processes and save the answers.
Record decisions and runbooks as pages.
Let history and receipts record change.
09Checklist
10Before and after
Without
With SyncOnAI 360
A document that goes stale
The org as the reference
A wiki apart from Salesforce
Pages beside the org
Decisions lost
Transcripts and decisions kept
History reconstructed
Receipts written for you
12Questions
The org itself is the reference, and the chat explains components on request; save the answers you want as pages.
Objects and fields are synced and searchable; ask the chat to describe an object and save the result as a page.
In the workspace, beside the orgs and projects.
Yes. Record a call in a browser tab; it needs an OpenAI key for now.
The repository refreshes every six hours; pages you write are yours to update.
Yes. Pages are searched and cited in answers.
Pages live in the workspace; health and audit reports can be shared as links.
Yes. Every plan includes every feature.
Projects have their own wiki; workspace pages sit alongside for documents that span projects.
They move to Trash, where they can be restored or deleted for good.
Yes. Pages belong to the workspace and are searchable by everyone in it.
The Canvas lens draws the data model for each org, alongside your written pages.
13Keep exploring
Connect your Salesforce org. Run your first health scan. Ask your first question. See what you've been missing.