Strongpoint's dependency relationship diagrams show you how different customizations are connected:
Detailed customization records show you everything you need to know about a customization — who created it, who has access to it, how it's changed and what it's connected to:
Create policies that monitor for changes to specific profiles or permission Sets — and log everything in audit-friendly reports. Strongpoint treats changes to user permissions the same way it treats other metadata — giving you a verifiable audit log showing who changed what and a full diff of what was affected:
A complex object in Salesforce may contain multiple custom fields, standard fields, formula fields, record types, picklist values, buttons and links.
Strongpoint gives you easy-to-work-with reports and spreadsheets showing all settings attached to an Object, profile or permission set:
Get an in-depth look at everything a user can see and do, find the permissions attached to a profile, and more — Strongpoint makes it easy to perform detailed reviews and determine who has access to in-scope financial data:
Strongpoint gives you detailed reports for analyzing the impact of a proposed change. Our impact reports show you all the customizations on a base record, as well as their dependencies. This method is particularly useful for investigating and reviewing changes in multiple customizations at once.
Strongpoint lets you build out specific change policies and approval requirements based on risk.
Here's the Strongpoint policy record, where we can specify which types of changes require a full SDLC, which require testing in the Sandbox, which require approval, which can be handled via a process issue, and which are simply logged, ie. they are safe and require no additional investigation:
Strongpoint automatically records every change in your Org and logs it in change logs. Change logs are an immutable, date- and time-stamped record, containing a full, detailed diff showing what happened, and when it happened.
Strongpoint is a true closed loop change management system. Every change to metadata is captured in an immutable log. Every completed change is reconciled back to an originating request and, if necessary, an approval.
Every change and approval is checked for compliance with the policies you’ve set out. Anything that doesn’t follow policy is captured in a noncompliant changes report for review and clearance.
The best part? Changes to your policies are logged and monitored using the same process. This makes it impossible to alter an approval after the fact or artificially resolve a noncompliant change.
In other words, the whole process is airtight and fully validated — something that’s critical to security, governance and audit readiness.
The 'What Changed' report is your at-a-glance record of all development activity in your Org.
See what happened and whether it followed policy — and link to Strongpoint's Change Logs for a full diff of the changes:
Strongpoint treats configuration data with the same scrutiny it applies to other Apex metadata in your Org.
Then, Strongpoint gives you a systematic way to focus on in-scope Objects and create highly granular policies to track and monitor them.
Strongpoint gives you the option of blocking risky changes without prior approval. This is often used for pricing and discount data which impact revenue directly. If a user attempts to make a change to a field that has blocking enabled, they will be unable to do so unless a change request has been submitted in advance.
In this screenshot, we can see that Strongpoint has automatically blocked a change to the 'Price' field in the Block Price customization because it didn't have an approved change request:
