Cloud Account Structure Planner

Plan accounts, projects and permissions.

Added October 15, 2026. Written with AI assistance and checked for clarity and placeholders; not reviewed by a lawyer, accountant, clinician or other professional. How these prompts are made

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it (what [VERIFY] means).

Plan the structure of cloud accounts or projects for my organisation. Provider: [CLOUD_PROVIDER]. Teams and products: [TEAMS_PRODUCTS]. Environments and data sensitivity levels: [ENVIRONMENTS_SENSITIVITY]. Existing accounts: [EXISTING_ACCOUNTS].

Propose a hierarchy as an indented tree (organisation, folders or units, accounts or projects) and justify each boundary by blast radius, billing, permissions, or compliance. Create a permissions matrix of roles by environment with least-privilege defaults, break-glass access, and approval requirements. Describe baseline controls applied to every account (logging, guardrails, budget alerts). Provide a migration approach from the existing accounts in phases with checks. State assumptions and mark provider-specific features [VERIFY] against current documentation.

Add a decision record format for the structure, listing the options considered and why each was rejected, so future changes are made knowingly. Provide a list of questions to settle with finance and security before building (billing owner, log retention, root account protection) and a checklist for a new account to meet the baseline on day one.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

• IAC