Approvals And Governance
Use this guide to set team expectations for reviewing, executing, rejecting, and auditing HubSpot write plans.
Approval Model
Section titled “Approval Model”Daeda AI keeps the final approval step inside HubSpot. A plan can be prepared by an assistant, but a user still reviews the plan and chooses whether to execute it.
Teams should agree who can execute plans, who can approve sensitive changes, and when a second reviewer is required.
Plan States
Section titled “Plan States”| State | Governance use |
|---|---|
| DRAFT | Review before execution. This is the main approval state. |
| EXECUTED | Review results and confirm the HubSpot outcome. |
| EXECUTING | Wait for completion before making related changes. |
| FAILED | Inspect operation results before retrying or revising. |
| REJECTED | Keep for comparison when asking for a better draft. |
| SUPERSEDED | Use the newer plan for review and execution. |
Sensitive Changes
Section titled “Sensitive Changes”Use extra review for deletes, archives, merges, broad record updates, schema changes, workflows, lead scores, reports, dashboards, and bridge-backed operations.
For sensitive changes, reviewers should confirm the target portal, affected assets, permissions, and intended rollback or follow-up path before execution.
Team Operating Practices
Section titled “Team Operating Practices”- Use narrow plans for risky work.
- Reject drafts that are too broad or ambiguous.
- Keep failed and rejected plans visible for support review.
- Confirm bridge-backed execution is enabled only for approved portals.
- Rotate license keys when workspace ownership changes.
After Execution
Section titled “After Execution”After execution, review operation results and inspect important HubSpot assets. If a plan partially completed, check what changed before asking for a retry or revised plan.