Skip to main content
The Soul Doc is a managed-workspace profile of your Salesforce org. When the capability is enabled for a workspace, it can summarize how the business runs, which automations matter, how the data model fits together, and where risks may need review. Treat it as generated context to review, not as a replacement for Salesforce source metadata, release documentation, or an administrator’s judgment.

​
What goes into it

When you generate a Soul Doc, ApexGenius reviews the synced metadata available to that project:
  • Business domain: what your company appears to do, inferred from objects, fields, and naming
  • High-impact automations: the Flows, triggers, and validation rules that actually shape behavior
  • Architecture patterns: how code and declarative automation divide the work
  • Data model: core objects, their relationships, and where custom objects fit
  • Risk areas: recursion hazards, unbounded queries, brittle integrations

​
Why it matters

A reviewed Soul Doc can give a connected AI client useful project context. It can help frame questions such as “What automations run on Account?” around the org’s own metadata. Always verify important conclusions against the underlying components.
If the capability is available in your workspace, generate the Soul Doc after the first metadata sync and review it before relying on it as project context.

​
How to generate one

  1. Sync metadata for the intended Salesforce project.
  2. Open the Soul Doc or Org Insights control shown in the workspace.
  3. Start generation and return to the workspace when it reports completion. Processing time varies by project and available metadata.
Regenerate after major org changes (a big release, a new managed package) so the profile stays honest.

​
Where it lives

The Soul Doc belongs to its Salesforce project. Availability and the way an AI client receives that context depend on the workspace and client configuration. Confirm the selected project and review the generated content before using it in an MCP task.
Last modified on August 28, 2026