> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/salesforce/overview.md). # Overview ## IZ Suite for Salesforce IZ Suite for Salesforce provides one unified platform for visibility, code analysis, and governance across Salesforce environments - helping teams understand their Apex codebase, uncover risks across orgs. ### Salesforce Development Challenges Salesforce orgs powered by Apex classes and triggers enable powerful customization, but teams often face key challenges: * Limited visibility into all Apex classes and triggers across environments. * Difficulty understanding dependencies between classes, triggers, and objects. * Hidden technical debt and unused or redundant code. * Inconsistent coding standards and lack of centralized governance. * Risky deployments causing unexpected runtime failures or performance issues. ### Solution: Apex Visibility and Governance IZ Suite brings automated discovery, deep code analysis, and governance to Salesforce — giving teams clarity and control over their Apex landscape. ### Key Benefits **Complete Code Visibility** – Discover and inventory all Apex classes and triggers across Salesforce orgs. **Improved Code Governance** – Enforce standards and detect violations before deployment. **Reduced Deployment Risk** – Identify breaking changes and risky patterns early. **Better Org Health** – Detect unused code, performance risks, and anti-patterns. ### Core Capabilities **Automated Discovery of Inventory** – Automatically scans and catalogs Apex classes, triggers, and related metadata. **Static Code Analysis** – Evaluate Apex code for best practices, security vulnerabilities, and performance issues. **Trigger Behavior Mapping** – Analyze trigger events (before/after insert/update/delete) and execution flow. **Governance & Policy Enforcement** – Assess Apex code against organizational standards and compliance requirements. **Change Impact Insights** – Understand what components may be affected before modifying or deploying code. ### Who It’s Designed For IZ Suite for Salesforce is aimed at: * Salesforce Architects * Apex Developers * DevOps and Release Managers * Enterprise Platform Owners responsible for governance and risk management * Security and Compliance Teams reviewing custom code --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-eye/salesforce/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.