Connect an agent and control its permissions
Give an AI agent access to one workspace with only the permissions it needs, review what it does and revoke it when done.
Start from the official developer connection instructions and check the server address. Authorize the account and the smallest set of capabilities needed for the task. Keep credentials in the supported connection flow; do not paste unrestricted secrets into a chat or a casa’s content.
A connection allows the agent to request permitted operations. It does not automatically approve every future change. Begin with inventory and a dry-run plan. Review the exact domains, content, casita changes, DNS records, expected charges and cost cap. Approve a specific current plan with a clear expiry before execution.
Watch the operation’s progress and inspect the per-domain results. A partial batch is not a successful full migration. Retry only the eligible failed items after checking whether the provider already performed an uncertain action.
To stop future access, revoke the connection or token in account settings. Also pause active jobs and inspect provider operations already submitted; revocation cannot undo a completed change. Keep the audit reference for support. If a plan changes after approval, require a fresh review before continuing.