Overview
Salesforce orgs accumulate hundreds of custom fields, half of which nobody fills in. Modus mines the objects you select with field-level metadata, statistics, and samples, so agents know which fields are real.
What Modus reads
- 1Org
- 2Object
- 3Field
You select the level Modus is allowed to mine. Everything below it is discovered automatically; everything outside it is never touched.
4context types mined
3agent tool groups
1connection method
5security controls
Context types
Each object Modus mines produces typed context items, addressed by their position in the hierarchy. This is what an agent actually receives.
Org object list
The objects available in the connected org.
Object metadata
Standard and custom objects with their labels and relationships.
Object statistics & samples
Record volumes and representative records.
Field metadata, statistics & samples
Field types, picklist values, fill rates, and sample values — so an agent can tell a live field from an abandoned one.
Example context item
salesforce_field_metadataacme-prod›Opportunity›Forecast_Category__c
- Type
- Picklist
- Values
- Commit · Best Case · Pipeline · Omitted
- Fill rate
- 96% of open opportunities
- Note
- Preferred over standard ForecastCategory
Common use cases
- 01
Get pipeline answers that use the custom forecast field the team actually maintains.
- 02
Join CRM accounts to warehouse revenue in one composed answer.
- 03
Stop an agent reporting on a deprecated stage picklist.
Connection method
Connect once. Modus stores credentials in a managed secret store, rotates what it can, and never asks an agent to handle them.
OAuth (managed)
Managed Salesforce OAuth. Access follows the profile and sharing rules of the connected user.
Security & governance
Governance is applied once, at the layer every agent runs through, so it holds no matter which agent asks.
Metadata-first mining
Modus learns from structure and usage, not bulk data. Raw records stay in your environment; only the metadata needed to understand the system is stored.
Scoped selection
You choose exactly which schemas, folders, spaces, or boards Modus is allowed to see. Nothing outside the selection is ever mined.
Read-only by default
Mining runs on a read-only credential. Any tool that writes back is a separate, explicitly granted action.
Data classification
Sampled values are scanned for PII, financial, health, credential, and government-ID patterns, then classified as Sensitive, Flagged, or Non-sensitive. Your own overrides win over the defaults.
Group access by sensitivity
Map your identity groups to sensitivity tiers so each team only ever composes context at or below its clearance.
