Skip to content
Book a build

Security & implementation controls

Read-only inspection.
Deliberate changes.

Working in a client’s HubSpot portal calls for clear boundaries: what is being inspected, what has been approved, which portal is in scope and what the run actually did.

01 / Inspection

Portal Audit reads. It does not implement fixes.

The audit evaluates portal configuration and produces scored evidence, findings and a branded report or PDF. A finding does not authorize a change. Your team decides what belongs in a separate implementation.

02 / Human decisions

Generation and deployment have separate approvals.

In Projects, review the plan before approving generation. Review generated assets and the proposed deployment before approving portal changes. A plan, an AI response and a deployment receipt are different artifacts—not interchangeable assurances.

03 / Access & scope

A workspace for the team. A portal for the Project.

Jetstack access is scoped to the signed-in organization. A Project is bound to a HubSpot portal, and the implementation works in that context. Review the active workspace, connected portal and destination before approving work; do not assume access to one portal authorizes another.

04 / Execution record

Inspect the run, not just the proposal.

Projects uses durable runs, dependency-aware execution and receipts with read-back verification. Check the actual result and any failed or incomplete work. An accepted plan is not evidence that all of its assets are live.

Before approving work

Check the connection and the context.

The technical connection and the implementation approval are separate things. Review both.

HubSpot connection

Know which portal is connected.

Jetstack uses HubSpot connections and, for supported internal-API work, the browser extension. Review the permissions requested when connecting and the portal the workflow targets.

Team access

Review your workspace membership.

Organization scoping is not a promise of a particular role hierarchy or approval policy. Discuss your team’s access requirements and review who can work in the connected workspace.

Portal reuse

A destination is its own implementation.

Matching assets and remapping IDs does not remove the need to review dependencies and references. Each destination portal’s mappings are reviewed before deployment, and a deployment can be rolled back.

Your security review

Ask about the details
your team needs.

Use the published policies for the legal terms. Bring questions about data handling, retention, subprocessors, access or infrastructure to the conversation rather than treating an implementation control as a broader security assurance.

This page does not claim a security certification, a specific hosting region, a blanket no-record-storage policy or AI-provider data terms.