Reads your org configuration and writes plain-language help for every object, grounded in how your org actually works rather than a generic template.
‹ Products
Clionyx
AI documentation for your Salesforce org
Role-specific Salesforce documentation, generated by AI from your real org.
Clionyx reads your Salesforce configuration and writes plain-language, role-specific documentation grounded in how your org actually works, so the docs reflect the real build instead of a generic template. Named after Clio, the muse of history.
How it works
From your org to living docs
What it does
Key capabilities
Role-specific documentation: the same object reads one way for a salesperson and another for a support agent, scoped to the layouts, record types, and fields each role can see.
Every factual claim is grounded in a specific piece of your configuration, so the docs are accurate rather than approximate.
Structured output per object: what it is for, your process steps, the fields you fill in, what connects to it, what runs automatically, what blocks a save, and a decoder for your real validation messages.
Written for the reader: field labels instead of API names, and the effect of automation ("when you mark Closed Won, an invoice task is created") instead of the mechanism.
On-screen collapsible sections plus a print-ready PDF leave-behind.
Your team reviews each document paragraph by paragraph (approve, edit, pin, reject, comment), and those decisions are remembered so your corrections compound across versions (rolling out).
A standard role library with an automatic profile-to-role proposal, plus per-role tailoring: glossary, suppression, injected content, emphasis, and tone.
Designed to detect org changes and refresh the affected docs, publish approved help into Digadop Help in context, and generate plain-language release notes from a change ledger (on the roadmap).
A REST API and an MCP server for programmatic generation (Growth and above, in development).
Who it is for: Salesforce documentation owners, admins, and enablement teams whose org docs go stale the moment a field or validation rule changes.
Sample output
A page of docs, written for the reader
DocOpportunity, documented for a Sales rep
- What it is forTracks a deal from first interest to closed.
- StageMove it along as the deal progresses. "Closed Won" is final.
- AmountThe expected revenue. Required before you can submit for approval.
- What happens automaticallyMarking Closed Won creates an invoice task for Finance.
Illustrative example. Clionyx writes field labels and the effect of automation in plain language, grounded in your real configuration. It is designed to only read your org and never writes to it.
Maturity
What is live, and what is coming
Available now
- AI generation of structured, role-specific documents from your org metadata, with every claim grounded to a specific configuration element.
- On-screen collapsible HTML and a print-ready PDF.
- Versioned, persisted runs per object and role, opening in a review state and visible in the portal.
- The role library, automatic profile-to-role mapping, and per-role tailoring (glossary, suppression, injection, emphasis, tone).
Coming soon
- Automatic refresh: watching the org and regenerating affected docs as it changes (today an admin triggers generation on demand).
- In-context delivery into Digadop Help on the page the user is on.
- A release-notes generator: a change ledger plus on-demand, shareable plain-language release notes.
- A REST API and MCP server for programmatic generation (Growth and above).
Trust
Built to be safe to connect.
Designed to only read
Connects through Salesforce OAuth and never writes to your org.
Your config, not your data
It documents your configuration and metadata, not your business record contents, and your content never trains a model.
AI on AWS Bedrock
Generation runs on Amazon Bedrock, and every document is reviewed on your terms before anyone relies on it.
See Clionyx in your org.
Part of the Digadop platform: one security and data model across the family.