Upgrading OrgGuard (Beta)

This applies only to OrgGuard beta installs

You’re reading this because you’re an early beta participant. Beta package versions can’t upgrade in place, so each new build is a guided uninstall → reinstall. This is not how OrgGuard normally updates — once OrgGuard ships on the released / AppExchange line, upgrades are automatic and in place: no uninstall, no data loss, and none of the steps on this page.

Overview

Salesforce treats beta managed-package versions as disposable: you cannot install a newer beta on top of an existing one, and you cannot upgrade in place. To move from one beta build to the next you uninstall the old version and install the new one. Two things on your org will block the uninstall until you clear them — an active OrgGuard flow and the OrgGuard permission set assignments — so this guide walks the full round trip in order.

This is a temporary, beta-only procedure. When OrgGuard reaches its released / AppExchange distribution, your org upgrades seamlessly in the background and keeps all its data — you won’t do any of this.

Who this page is for

The Salesforce System Administrator moving an existing OrgGuard beta install to a newer beta build. If this is your first OrgGuard install, you don’t need this page — see Installation instead.

Uninstalling removes all OrgGuard data

Uninstalling the package deletes everything OrgGuard stored in your org — discovered assets, findings, notifications, policies, your Setup configuration, and the certificate/scheduled-job audit history. Salesforce offers a “Save a copy of this package’s data for 48 hours” option during uninstall, but that’s an export for your records only — reinstalling does not restore it. Plan to re-scan and re-configure after upgrading. (This data loss is another reason in-place released upgrades — which preserve everything — are the future state.)

What you’ll see

You’ll work almost entirely in Salesforce Setup, across three screens:

• Setup → Flows — a list of your org’s flows. The OrgGuard SJH Daily Poll row shows status Active with a ▾ action menu; this is the flow you deactivate.
• Setup → Installed Packages → Uninstall — the uninstall confirmation screen, with an optional Save a copy of this package’s data for 48 hours checkbox and a confirmation button.
• Setup → Installed Packages (after reinstall) — OrgGuard reappears in the list, now showing the new version/build number.

You’ll also use Setup → Permission Sets (to remove and re-add assignments) and the in-app OrgGuard → Setup tab (to re-run the wizard).

What you’ll need

• System Administrator access to the org.
• The install link and installation key for the new version — the OrgGuard team provides these with each beta build. (Beta installs always require the key.)
• A few minutes — uninstall and install each take a short while and Salesforce emails you when they finish.

Common tasks

Task: Upgrade to a new beta build

Who can do this: Salesforce System Administrator.

Prerequisites: the new version’s install link + installation key; you’ve accepted that current OrgGuard data will be wiped (see the caution above).

1. Deactivate the OrgGuard flow. Go to Setup → Flows. Find OrgGuard SJH Daily Poll, click the ▾ at the end of its row → View Details and Versions (or click the flow name). In the Flow Versions list, click Deactivate next to the Active version.

   Caution

   This step is required. Salesforce blocks a managed package from uninstalling while one of its flows is active — skipping it produces “The flow is still active. Deactivate the flow, and try again.”

2. Unassign the OrgGuard permission sets. Go to Setup → Permission Sets. Open OrgGuard Admin → Manage Assignments → select every assigned user → Remove Assignments. Repeat for OrgGuard User and OrgGuard Auditor if anyone is assigned to them.

   Caution

   Also required — Salesforce won’t delete a permission set that’s still assigned (“This permission set is assigned to one or more users…”). Write down who was assigned to which set so you can re-grant them in step 5.

3. Uninstall the old version. Go to Setup → Installed Packages, find OrgGuard, and click Uninstall. You may optionally tick Save a copy of this package’s data for 48 hours (export only — see the caution above). Confirm. Uninstall runs for a few minutes and Salesforce emails you when it completes.

4. Install the new version. Open the install link the OrgGuard team gave you, enter the installation key, and install (Admins-only, or for all users per your policy). OrgGuard’s post-install runs automatically — it recreates the Setup record, schedules the four Apex jobs and re-activates the OrgGuard SJH Daily Poll flow (five scheduled jobs in total), re-seeds the two default Scheduled Job Health policies, and re-assigns OrgGuard Admin to you (the installer). See the Post-Install Checklist for the full list.

5. Re-grant the permission sets you removed in step 2. Setup → Permission Sets → the relevant set → Manage Assignments → Add Assignment → select the users → Assign. (The installer already has OrgGuard Admin from step 4; this is for everyone else.)

6. Re-run the Setup Wizard. Open the OrgGuard app → Setup tab and complete the wizard. This re-applies your policies, schedule, and email/Org-Wide Address settings, and re-owns all the scheduled jobs to your admin user — the Schedule step re-owns the discovery scan, and the Complete step re-owns the notification and housekeeping jobs.

   Don’t skip this — your alerts depend on it

   On a fresh install the scheduled jobs are owned by the package’s system user, which has no field access and silently fails. If you skip the wizard, scans may run but no email or in-app alerts will arrive. If alerts are the only thing you need to restore and you don’t want to re-run the full wizard, click Reschedule monitoring jobs on the Setup tab — but that only re-owns the notification and housekeeping jobs. Re-owning the discovery scan still requires completing (or re-running) the wizard’s Schedule step.

7. Run an initial scan. From the Setup tab or the Scans tab, trigger a discovery scan to rediscover your assets and regenerate findings — everything was wiped on uninstall.

Expected result: the new version appears under Setup → Installed Packages; all OrgGuard scheduled jobs show your admin user as owner under Setup → Scheduled Jobs; a fresh scan produces assets and findings; and a test alert (or the next notification digest) is delivered.

Troubleshooting

Symptom	Likely cause	Fix
Uninstall fails: “The flow is still active.”	The OrgGuard SJH Daily Poll flow is still active.	Deactivate it — step 1 above.
Uninstall fails: “This permission set is assigned to one or more users.”	An OrgGuard permission set is still assigned.	Remove all assignments (Admin/User/Auditor) — step 2 above.
New version won’t install over the old one.	Beta versions can’t upgrade in place.	You must uninstall the old version first (steps 1–3), then install.
Scans run after upgrade but no email/in-app alerts arrive.	The scheduled jobs are still owned by the package system user (no field access).	Re-run the Setup Wizard, or click Reschedule monitoring jobs on the Setup tab — step 6.
All my assets, findings, and history are gone after the upgrade.	Expected — uninstall wipes all package data.	Run a fresh scan (step 7) and reconfigure. Released upgrades (future) preserve data.
Installer didn’t get OrgGuard Admin after reinstall.	Rare non-fatal post-install warning.	Assign it manually: Setup → Permission Sets → OrgGuard Admin → Manage Assignments → Add Assignment.

FAQ

Will I lose my data when I upgrade? Yes. A beta upgrade is an uninstall + reinstall, and uninstalling removes all OrgGuard data — assets, findings, notifications, policies, configuration, and audit history. Re-scan and reconfigure after installing the new build.

Why can’t I just upgrade in place like a normal app? Because these are beta package versions, which Salesforce treats as disposable — they can’t be upgraded in place and can’t be installed over each other. This is a platform rule for beta versions, not an OrgGuard limitation.

Do I have to do this for every new build? While you’re on the beta line, yes — each new beta build is a fresh uninstall/reinstall.

When do upgrades become seamless? When OrgGuard moves to its released / AppExchange distribution. Released managed versions upgrade in place — Salesforce installs the new version over the old one in the background, migrating your flows, permission sets, and data automatically. No uninstall, no data loss, none of the steps on this page.

Do I need the installation key every time? Yes — beta installs always require the installation key the OrgGuard team provides with each build.

Related

• Installation — first-time install
• Post-Install Checklist — what runs automatically after install
• Setup Wizard — the post-install configuration flow (and where jobs get re-owned)
• Permission Sets — role-to-permission-set mapping
• Scheduled Jobs — what each scheduled job does
• Notifications — verifying alert delivery