One system, four ways of looking at your account.

Every fix starts as a preview. Kronavi shows you the current state of the entity, the proposed new state, and what's different between them, the same way you'd read a code diff. If the fix is to re-point a workflow action at the correct trigger, you see both trigger references side by side. If the fix is to clean up a form that sends to a retired tag, you see the tag being removed and the replacement tag, if any, that will go in its place. You can edit the proposed change, approve it as drafted, or discard it and move on — the three options sit next to each other so the decision is a single click either way.

The moment you approve, Kronavi captures a one-click undo point and only then makes the change inside your GoHighLevel account. If the fix doesn't land the way you expected — a downstream workflow behaves differently, a client calls about a message that stopped going out — you roll back from the same panel that showed you the preview. Nothing is ever permanent without your sign-off, and nothing is ever un-reversible.

You can also chain fixes. If the audit surfaced twelve findings and you want to clear all of them in one pass, Kronavi drafts twelve previews and lets you approve them in a single confirmation rather than twelve separate clicks. Every one of them still carries its own undo point, so approving a batch doesn't forfeit per-fix rollback.

A snapshot captures the workflows, pipelines, forms, automations, tags, and calendars inside an account at a precise moment. Not a screenshot — the actual state of the entities, stored so you can restore from them later. Kronavi takes one automatically before every fix, and you can take manual snapshots before bigger changes you're making by hand inside GoHighLevel or when a client is about to hand an account over to a new operator.

When you compare two snapshots, you see exactly what changed in the account between them, entity by entity. Workflow added, trigger renamed, pipeline stage reordered, form field removed. Every change is labeled with when it happened and which snapshot pair made it visible, so you can walk backward through the history of an account even when no one left notes about what they changed or why. This is how you answer the "who touched this and when" question that normally takes forty minutes of GoHighLevel audit-log scrolling.

Restoring is entity-level. You don't have to roll the entire account back to recover one workflow — pick the workflow, pick the snapshot you want to restore it to, and Kronavi replays only that entity. The rest of the account stays where it is. A failed bulk edit, a mis-approved fix, a client who changed their mind about a rewrite: all recoverable in one click without disturbing anything else.

The portfolio view is the first thing an agency owner sees. Each sub-account is a tile: its name, its current health state, the count of critical and revenue-risk findings, and the time of its most recent audit. Sorting is by severity by default, so the accounts that need attention this morning are always at the top. Twelve sub-accounts, three minutes, one summary — you open your laptop and you already know where today's work is.

Drilling into any tile takes you to that account's full audit, exactly the same view you'd see if you were auditing that account on its own. Fixes you approve at the account level still carry their preview, their undo point, and their snapshot — multi-sub doesn't downgrade any of the single-account protections. You can also run a fix across multiple accounts at once when the finding is the same: the same retired tag showing up in five sub-accounts' intake forms becomes a single batched preview that lets you clear all five with one approval.

The rollup stays current on its own. When you rerun an audit on one account, its tile updates; when you run audits on every account, the whole view recalculates. You don't need to remember which sub-account was last touched or which one is due for a check — the view tells you, in the same language across every account, so switching between twelve clients doesn't cost you twelve context rebuilds.