Admin Lifecycle
Use this guide when a HubSpot administrator installs Daeda AI, grants more access, changes ownership, reconnects a portal, or removes access.
Install Prerequisites
Section titled “Install Prerequisites”- Confirm the user can install or manage HubSpot apps for the target portal.
- Confirm the user can open the Daeda AI installed app settings.
- Confirm billing ownership before connecting more portals than the current plan includes.
- Confirm whether any planned work needs the Daeda Bridge extension.
- Start with the smallest useful data access set, then add groups as real work requires them.
Daeda AI currently requests these required install scopes before optional connected-portal access is added:
| Scope |
|---|
| crm.schemas.companies.read |
| crm.schemas.contacts.read |
| crm.schemas.deals.read |
| oauth |
| tickets |
Re-Authorize Access
Section titled “Re-Authorize Access”Re-authorization is used when a plan or connected portal needs HubSpot access that has not been granted yet. Do it from the visible prompt in Daeda AI, then reload the plan or connected portal status before execution.
Re-authorize only when the requested access matches the work the user wants Daeda AI to perform. If the requested access is broader than expected, reject the plan and ask for a narrower draft.
Reconnect Or Change Owner
Section titled “Reconnect Or Change Owner”When admin ownership changes, review the connected portal, license key, billing owner, and bridge toggle together. A workspace that can prepare plans should be owned by the team that is allowed to review and execute those plans.
Use this checklist after an ownership change:
- Rotate the license key if the previous workspace owner should no longer prepare plans.
- Confirm the target portal still appears in Connect Client Portal.
- Confirm granted access still matches the team’s intended scope.
- Confirm bridge-backed execution is enabled only for portals that need it.
- Reject stale draft plans that were prepared for an old owner or old process.
Remove Access
Section titled “Remove Access”Before uninstalling or removing access, review active draft plans. Reject drafts that should not remain executable, rotate license keys, and confirm there are no bridge-backed workflows in progress.
After access is removed, users should treat existing plan results as historical records. New plans require a current license key, connected portal, and HubSpot authorization.