> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/aws-joining-pump/aws-multi-account-architecture/join-via-cta.md). # Join via CTA Some customers have certain organizational and/or security level constraints that require a different onboarding process. For those customers we can onboard them via a Consent To Assign Agreement (CTA). A CTA is a process for moving the account ownership and billing of the organization management account from the customer to Pump.\ \ **Step 1: Discovery** * Pump will do discovery on a call with the potential customer to determine if CTA is right for them. This will be at Pump's discretion and is not available to all prospects. * The customer will deploy the read-only stack and run the estimate to determine if they'd be interested in joining Pump. \ **Step 2: CTA** * Once the customer is ready to join Pump, Pump will present them with the CTA agreement. * The customer will update the root user email address of the management account to a provided email address. * Pump will update the billing details of the management account to Pump's details. \ **Step 3: Onboarding** * The customer will deploy the auto-pilot stack to allow Pump access to their billing and savings. * That't it!! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.pump.co/aws-joining-pump/aws-multi-account-architecture/join-via-cta.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.