Use case · Salesforce consultancies
The same security review for every client org.
One method for every engagement: the same checks, a baseline on day one, and a report the client can keep.
Running many client orgs? Talk to us and we will set up a workspace that fits.
01The problem
Every review starts from a blank page.
The work is skilled. The method is often a spreadsheet and the memory of whoever ran the last one.
- Reviews do not compareTwo consultants on two orgs check different things.
- No before and afterIt is hard to show what you fixed, and what was broken when you arrived.
- Evidence is screenshotsClients and their auditors want the file, the setting and the path.
02How Vulkro helps
Every client org, read the same way.
Each org gets four numbers with their change since last month and a short list of what to fix next. The next scan shows what your team closed.
- Four numbers per client orgWhat is wrong in plain words the client can read, the same four on every engagement.
- The change since last monthEach number shows whether the org got better or worse since the last report.
- What to fix nextA short list with a key and an owner, so the client team can start.
An example org, Acme Production. Names and figures are illustrative.
03Why it holds up
Precise, and checkable.
- 01753 checks, every time147 on the live org and 606 on code and metadata, the same on every engagement.vulkro-sf checks, vulkro-sf 0.28.0
- 02Measured, not claimedA baseline on day one, then what is new against what was fixed when the engagement ends.Baselines
- 03Nothing installedThe org is read through your own Salesforce login, read-only. Code and metadata scans run on your machine.Live-org reads are part of Pro