> ## Documentation Index > Fetch the complete documentation index at: https://docs.lightspark.com/llms.txt > Use this file to discover all available pages before exploring further. # Overview > Experimental native Grid functionality for connecting AI agents to Global Accounts with managed policy and approval flows export const FeatureCardGrid = ({cols = 3, children}) =>
{children}
; export const FeatureCard = ({icon, title, children, href, linkHref, linkText, color, tag, tagPosition, layout, variant, iconSize}) => { const isHorizontal = layout === 'horizontal'; const isFlat = variant === 'flat'; const isLargeIcon = iconSize === 'lg'; const isInlineTag = tagPosition === 'inline'; const card =
{icon &&
{color ?
: }
}
{isInlineTag ?
{title} {tag && {tag}}
:
{title}
}
{children}
{tag && !isInlineTag &&
{tag}
} {linkText &&
{linkHref ? {linkText} : {linkText} }
}
; return href ? {card} : card; }; This section describes experimental Grid functionality. Details may evolve as the agent product surface expands. Agent connectivity is currently limited availability. To request access, [book a demo](https://www.lightspark.com/contact) or reach out to your Lightspark contact. Use Grid-managed agent connectivity to let your users connect AI agents to Global Accounts. The connected agent may run in your product, on the user's device, or through a third-party tool such as OpenClaw or Codex. Grid does not run the agent runtime. Grid powers install, delegated credentials, policy evaluation, approval state, and execution boundaries for agent-initiated actions, while your product surfaces the connection, approval, and history experience to the end user. ## Design principles Delegation does not transfer account ownership. The customer can still require approvals, pause access, or revoke the agent entirely. Permissions, spend limits, account restrictions, and approval thresholds are evaluated by Grid before any agent-initiated action executes. Agents operate with a narrow, explicit capability set such as viewing balances, preparing withdrawals, or initiating transfers under Grid-defined controls. Every agent-initiated action stays traceable through Grid policy decisions, approval state, and final settlement outcomes. ## How it works In this model: * The customer still owns the Global Account and remains the ultimate authority over outbound movement. * You let users connect one or more AI agents they already use to their Grid-backed account experience. * The connected agent may run in your app, on the user's device, or through a third-party tool. * Grid powers agent install and delegated credentials for the connected agent. * Grid manages the agent's allowed capabilities, evaluation rules, and approval requirements. * The agent can propose or execute only the actions Grid allows for that customer and account scope. * Your surfaces remain the place where users view connection status, review permission requests, and inspect agent history. ## System flow ```mermaid theme={null} sequenceDiagram participant U as User participant P as Partner app participant G as Grid participant A as Connected agent U->>P: Connect agent P->>G: Start Grid-powered install flow G-->>P: Agent connection + delegated credentials A->>G: Request action Note over G,P: If approval is required G-->>P: Permission request P-->>U: Show approval UI U->>P: Approve or reject P->>G: Send decision G-->>P: Action executed automatically or after approval G-->>P: Activity, transaction, and audit updates ``` ## Typical flow 1. Your platform creates or links a Global Account for the customer. 2. The customer connects an existing agent through a Grid-powered install flow embedded in your product. 3. Grid creates the agent connection, provisions delegated credentials, and saves the configured policy. 4. The agent requests an action such as creating a quote, creating an external account, or executing a withdrawal. 5. Grid applies the saved policy for that connection. 6. The request is either denied, executed automatically, or delivered to your product as a permission request. 7. Your user reviews the request in a trusted surface you control. 8. Grid then sends the resulting activity, transaction, and settlement updates back to your product. ## Where Global Accounts fits This functionality is a natural extension of Global Accounts because outbound money movement already assumes customer-level authorization. Agent access adds a delegated actor while preserving the user's ownership and approval model. ## What you surface Your product should surface: * Agent connection state and metadata * Policy configuration and permissions screens * Approval and decision UX presented to end users on demand * Agent activity, audit records, and transaction history * Consumption of Grid events, [webhooks](/global-accounts/platform-tools/webhooks), or approval callbacks * Customer messaging and notification design ## Next steps Define what a connected agent can do, which accounts it can access, and when Grid requires approval. Design the approval and history experience your users see in your app or dashboard.