Designed to read your org configuration and write plain-language help for every object, grounded in how your org actually works rather than a generic template.
Clionyx
AI documentation for your Salesforce org
Role-specific Salesforce documentation, designed to be generated by AI from your real org.
Clionyx is designed to read your Salesforce configuration and write 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 role-specific docs
What it does
Key capabilities
Role-specific documentation: designed so 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.
Designed to trace every factual claim to a specific element of your configuration, so a reviewer can check any statement against the org instead of taking it on trust.
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.
Designed for your team to review each document paragraph by paragraph (approve, edit, pin, reject, comment), with those decisions remembered so your corrections compound across versions.
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.
Designed to offer a REST API and an MCP server for programmatic generation.
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 is designed to write field labels and the effect of automation in plain language, grounded in your real configuration.
Availability
What the beta includes
Availability: Clionyx is not yet generally available, and no Salesforce org can be connected to it yet. This describes Clionyx as designed and being built, not a service you can use today.
Trust
Built to be safe to connect.
Standard Salesforce OAuth
Designed to connect through standard Salesforce OAuth.
AI on AWS Bedrock
In production, generation will run on Amazon Bedrock, and every document is reviewed on your terms before anyone relies on it.
Sign up for the Clionyx beta.
Part of the Digadop platform: one security and data model across the family.