AI documentation & Push to Salesforce
Generate field descriptions with AI, review them, and write them back to Salesforce.
Most orgs have hundreds of undocumented custom fields. SchemaForce drafts descriptions for them with AI, lets you review every one, and — when you're ready — writes the accepted ones back into Salesforce. You stay in control: nothing is generated without a prompt, and nothing is pushed without your confirmation.
Drafting is read-only; pushing is the one opt-in write
Generating and reviewing descriptions never touches your org. The only write SchemaForce makes is the explicit Push to Salesforce action, and it only ever fills empty descriptions — it never overwrites one you already have.
Start from Needs Attention
The Needs Attention cleanup view buckets fields that need a look:
| Bucket | Fields it surfaces |
|---|---|
| Undocumented | No description or help text |
| Unused | 0% populated (field usage) |
| Barely used | Very low population |
| On no layout | Not exposed on any page layout |
| Looks like PII | Likely personal data (PII detection) |
| Likely duplicates | Fields that appear to overlap |
The Undocumented bucket is where AI documentation starts.
Generate, review, push
Generate
On the Undocumented bucket, Generate AI-drafted descriptions (and help text) for undocumented custom fields. The AI infers a plain-language purpose, synonyms, and a category — and abstains when it isn't confident rather than guess.
Common standard fields are documented from a curated dictionary with no AI call — that path is always free and doesn't count against your AI allowance.
Review
Every draft is yours to accept, edit, or dismiss — nothing is applied automatically.
The field page also carries a "Field meaning" enrichment (purpose / synonyms / category) that admins can correct directly. Correcting it locks the field from re-generation, so your wording sticks.
Push to Salesforce
Push to Salesforce writes accepted descriptions and help text back into the field's metadata. It's fill-empty only: it writes only when Salesforce's value is empty and never overwrites an existing description — those are reported as skipped.
Push one field at a time or in bulk. Every push is recorded in the workspace Activity log.
Knowing where a description lives
On the field page, a description's badge tells you its state:
- Authored in SchemaForce — an AI-authored description that lives in SchemaForce.
- In Salesforce — that description has been pushed back to the org.
What pushing requires
Writing back to Salesforce needs both:
- The connected Salesforce user must have the Customize Application permission. (See Connect your Salesforce org for connection permissions.)
- You need workspace settings-manage permission.
Plans
Free vs. Pro
Free includes 25 AI-drafted descriptions — curated standard-field documentation doesn't count toward that. Pro and Business are unlimited. Write-back (Push to Salesforce) is a Pro feature. See Plans & billing for the full breakdown.