Roadmap & Known Issues

This page tracks what’s coming next for OrgGuard and the known issues we’re working on. For what’s already shipped in each release, see the Release Notes.

Forward-looking

Items below describe planned direction, not a commitment to a specific date or release. We update this page as features ship and issues are resolved.

Coming soon

Planned enhancements for upcoming releases:

• Visual dependency graph — an interactive node-and-edge view of what depends on each certificate, alongside today’s dependency list, so you can see an expiry’s full blast radius at a glance.
• Type-specific asset detail views — detail screens tailored to each asset type (Scheduled Jobs, Connected Apps, Auth Providers) instead of the shared certificate layout. (Resolves the first known issue below.)
• In-app manual asset entry — add governance-relevant assets that automatic discovery can’t see (external certificates, vendor credentials) directly from the Inventory tab.
• Automatic owner attribution — OrgGuard suggests likely owners for discovered assets to reduce Missing Owner findings.
• Starter dashboards — packaged dashboards in the OrgGuard Dashboards folder (coverage, findings trends, certificate expiry timeline) so you get visual rollups on install.
• Tier indicator in the app — see your current tier (Free / Pro / Pro+) at a glance in the OrgGuard app.
• External Client App (ECA) discovery — extend auth-asset coverage to External Client Applications.
• Inbound mTLS certificate discovery — feature-enabled orgs will reliably surface their inbound mutual-authentication (mTLS) certificates in the inventory and CLM views. The current release does not yet detect them dependably even when the Salesforce feature is enabled; Pro 1.1 corrects this.

Known issues

We’re aware of the following and have a fix in progress for each.

Non-certificate assets show a certificate-style detail view

When you open a Scheduled Job (or another non-certificate auth asset) from the Inventory, the detail page currently displays certificate-specific fields (Fingerprint, Key Size, Signature Algorithm, SANs) and a certificate-worded Blast Radius tab. The underlying data is correct — those fields simply don’t apply to that asset type, so they appear blank. (Display issue only — no impact on data accuracy.)

Status: fix in progress — type-specific detail views are on the roadmap above.

Inbound mTLS certificates not discovered on feature-enabled orgs

If your org has the Salesforce mutual authentication certificate feature enabled (via a Salesforce support request), the current release does not yet reliably surface those certificates in the inventory — they show as zero regardless of scan result, with no error. Outbound and Connected App JWT certificate discovery are unaffected.

Workaround: None in the current release. Status: fixed in Pro 1.1 (discovery now reads the correct Salesforce Metadata API source) — see “Coming soon” above.