Limitations and invariants

Below are guidelines for how projects and organizations are used, with the rationale for each:

• You cannot move a project to another organization. This ensures consistent auditing and billing.
• A resource must exist inside a project. This enforces consistent governance and accurate quota attribution.
• The folder feature may be disabled. It is entitlement-based and controlled by a feature flag.
• Each customer account has exactly one organization. This simplifies external billing and contractual mapping.
• You can create up to 2,500 projects per organization.
• Project names within the same organization do not need to be unique.