On this page
A useful portal report needs to answer two different questions: what does the configuration show, and what should the team do about it? Portal Audit helps organize the first and informs the second. It does not grant itself permission to make changes.
This article was originally published in February 2026. The update describes the current workflow without carrying forward earlier, unconfirmed coverage counts. Available evidence depends on the selected checks, the connected portal and the access available.
Read-only means the audit is not the implementation
Portal Audit reads the connected HubSpot portal. Running it is not approval to create properties, rewrite workflows, merge records or change settings. That boundary matters when assessing a prospect’s portal, taking over from another team or agreeing an implementation scope.
Read-only access is still access. Obtain authorization to connect the intended portal, confirm the scope and agree who should see the report. “It does not write to HubSpot” is not a substitute for those decisions or a blanket security guarantee.
A score summarizes the measured evidence
Scoring uses defined rules and weights. AI-written commentary is a separate layer; the prose does not set the score. Keep that distinction when explaining a result to a client.
A score is also not a complete business diagnosis. The interpretation depends on the checks included and what the run could observe. A missing or unavailable result should lead to a question about coverage, not an assumption that the area passed. Review incomplete checks and warnings before treating a report as the baseline.
When comparing runs, keep the template and scope consistent and note any access changes. Otherwise a movement in the overall result may reflect a different review rather than a different portal.
Findings need an owner’s context
AI-assisted findings help explain measured values and propose next steps. Read them alongside the underlying evidence. They cannot establish why a company chose a process or whether a seasonal workflow should be retired.
For each important finding, ask:
- Which observation supports it?
- Is that observation complete enough to act on?
- Who owns the affected process?
- Could another asset or integration explain the behavior?
- What would demonstrate that a change actually helped?
Treat the generated wording as material to review, not a claim to publish unchanged. A clear report can say “needs investigation” where the evidence does not support a stronger conclusion.
Build a report a client can use
Portal Audit supports branded reporting and PDF output. Branding helps make the deliverable part of an agency engagement; it does not make every recommendation correct.
A practical handover separates the executive explanation from the implementation detail. Summarize the main decisions, preserve the evidence behind them and identify exclusions. Avoid presenting every flagged item as a defect. A nonstandard setting may be deliberate, and a low-use asset may still support an important process.
Before sharing, check the intended audience, wording, portal identity and selected content. Use the available sharing controls appropriately and confirm the recipient’s access through your engagement process. This article makes no claim that a report format satisfies a particular compliance requirement.
Make repeat reviews comparable
A saved audit template can help a team use a consistent review scope. Record the template, run date and any exceptions with the report. Repeatability is about explaining what was checked, not promising identical results across changing evidence or product versions.
For workflow-focused work, pair the broader report with a review of enrollment rules, references and overlapping property writes. A summary can surface an issue; the person approving a repair still needs to understand the affected path.
An audit finding is not an automatic fix
After review, turn an agreed finding into a separate work item. Define the desired behavior, affected assets, acceptance checks and approval owner. Some findings require a business decision rather than a software change.
Projects provides a portal-scoped implementation workflow with reviewable plans and separate generation and deployment approvals. Dependency-aware runs, receipts and read-back verification help account for the work performed. They do not remove the need to test business behavior after a write.
Use the report to decide what deserves attention. Use an approved implementation process to decide what changes. Keeping those decisions separate is the point.