Use this glossary when a user needs plain-language definitions for Daeda AI, MCP Pro, write plans, connected portals, permissions, and bridge status.
| Term | Meaning |
|---|
| Daeda AI | The HubSpot app where users review plans, connect portals, manage keys, and handle billing. |
| MCP Pro | The connected MCP service that lets an assistant prepare HubSpot write plans for review. |
| Write plan | A proposed set of HubSpot changes that waits for human review before execution. |
| Operation | One change inside a write plan, such as creating a list, updating a property, or deleting a report. |
| Connected portal | A HubSpot portal linked to Daeda AI for selected data access and plan execution. |
| License key | The key used to connect an AI app or workspace to Daeda AI. |
| Daeda Bridge extension | The browser extension used for actions that require an active HubSpot browser session. |
| Bridge-backed action | A supported action that needs the Daeda Bridge extension before it can execute. |
| Portal toggle | The connected-portal setting that allows or blocks bridge-backed execution for that portal. |
| Term | Meaning |
|---|
| Scope | A HubSpot permission granted to Daeda AI during authorization. |
| Required scope | Access requested during the first app authorization. |
| Optional scope | Access requested later when a portal connection or plan needs more HubSpot coverage. |
| Data access group | A selectable group of HubSpot data types, such as contacts, companies, deals, lists, or automation. |
| Re-authorization | Approving additional HubSpot access when a plan needs permissions that are not currently granted. |
| Mirror config | The connected-portal setup that records which HubSpot data groups Daeda AI should prepare for planning. |
| Granted access | The HubSpot permissions currently available to Daeda AI for a portal. |
| State | Meaning |
|---|
| DRAFT | A plan is ready for review and has not changed HubSpot yet. |
| EXECUTED | Execution completed and results are available. |
| EXECUTING | Execution has started and the plan is being applied. |
| FAILED | Execution stopped or finished with an error that needs review. |
| REJECTED | A user declined the plan instead of executing it. |
| SUPERSEDED | A newer plan replaced this plan. |
| State | Meaning |
|---|
| BUILDING | Daeda AI is preparing or refreshing mirrored data. |
| FAILED | The latest data preparation did not complete successfully. |
| IDLE | No data preparation is running. |
| PARTIAL | Some mirrored data is available with gaps. |
| READY | Mirrored data is ready for use. |