Documentation

1. Prerequisites

Salesforce editions. No edition constraint is established: the package is built and tested on Developer scratch orgs, no class queries the edition type, and no install on Professional or Enterprise has been measured. Do not infer that all of them are fine: the matrix has not been established, and we do not claim it. Tell us your edition when you ask for the trial; the trial install goes on a sandbox first.

API version. 67.0. Second-generation managed package (2GP), namespace orgguardian.

On the installing user. Your org's package-install rights. On whoever configures afterwards. The platform privilege “Customize Application” or the shipped custom permission OrgGuardian_Manage_Features, carried by the OrgGuardian_Admin permission set. The package never grants it to itself: the platform decides.

2. What the package puts in your org

70 objects and types: 19 custom objects (findings, activities, metrics, attestations, views, no-code configuration), 6 custom settings, 7 history Big Objects, 37 custom metadata types (gates, rules, regulatory mappings), 1 platform event. Tabs, a Lightning app, two permission sets (OrgGuardian_Admin, OrgGuardian_Viewer). No outbound flow active at delivery, no named credential needed for the first scan.

3. The first scan

Open the console: the recurring scan schedules itself on first opening, and the first findings arrive within the hour. At install, only the Discovery gates are open (limits, health and failed logins supervision); your licence key opens the rest with no reinstall. The 30-day trial opens the full plan, once per org.

4. What is optional, and not a prerequisite

• Shield / Event Monitoring: not required. When present, it switches on an optional tier of log detectors — which stays disabled by default.
• Hosted viewer: an option from the Small business tier up, disabled at install, enabled by an administrator after explicit consent, and sending only health aggregates with no personal data.
• External channels (Slack, Teams, PagerDuty, webhook), SIEM, ITSM: each opens separately, to a destination you choose, with your own credentials.

5. What an uninstall destroys

Everything. Uninstalling a managed package removes its objects and their data: findings, history, metrics, signed attestations, views, configuration. Salesforce keeps neither a recycle bin nor a restore. Before uninstalling: export findings and attestations as CSV and the configuration as JSON from the console, and rehearse once on a sandbox to measure what you get back. No export path reads the history Big Objects: that is documented, not hidden.