Guide / AIGIS resources
Salesforce Shield strengthens encryption, event monitoring, and field audit on the platform. It is not designed to record whether an AI model was permission-checked before it saw business context. AIGIS adds that evidence. Salesforce is the production proof path.
Executive read
Shield and AI governance answer different questions; they are complementary.
Shield hardens the platform; provenance records the AI access decision.
Keep evidence of the permission check before model exposure.
Salesforce is production-grade; ServiceNow and SAP are disclosed co-development.
Analysis
Shield helps with platform encryption, monitoring, and field history. Those are valuable controls for the system itself.
AI governance asks a different question: before the model saw a record, was the requesting user allowed to see it, and what evidence remains.
Teams that run Shield can still lack a per-interaction record of the AI access decision. AIGIS adds that record on top of the Salesforce permission model.
The two work together: Shield on the platform, permission-provenance on the AI access path.
See the provenance record on a real Salesforce workflow at `/demo`.
Resource packet
Evidence packet
Capture user context, system of record, enforcement tier, stripped fields, model route, response, hash marker, and fallback notes.
Salesforce is the production proof path. ServiceNow and SAP are design-partner co-development paths with asymmetric enforcement that must be disclosed in diligence.
Keep reading
Salesforce
Controls for reducing Salesforce data leakage risk in LLM-based workflows.
Salesforce
Why live Salesforce record visibility matters when assembling AI context for CRM workflows.
Audit
The audit elements needed to explain what an AI answer was allowed to know.