# Múltiplas contas

If your company has a multi-account architecture, we recommend calculating the savings estimate on Dotted first using your management account. This will provide us with a fairly accurate estimate of your potential savings.

Your management account is your 'root account' that you created your AWS account with, you can also verify this by visiting this [link](https://us-east-1.console.aws.amazon.com/organizations/v2/home/accounts) and seeing which account is designated as 'management account'.

<figure><img src="https://content.gitbook.com/content/hVJtws2byEHpNHKSxOHQ/blobs/4stsm8TbSYtkdz9JBk1F/image.png" alt=""><figcaption></figcaption></figure>

Once you've checked your savings with your management account following the steps listed in [Getting started](https://help.usedotted.com/como-comecar/etapas), assess if you'd need to be breaking your organization or importing it whole.

{% hint style="success" %}
If you have one or more active accounts within your AWS organization (like the example shown above) and don't have SSO setup - we recommend you disassociating your accounts from the organization & join the standalone account via the steps linked [here](https://help.usedotted.com/como-comecar/multiplas-contas/via-join-account-s).
{% endhint %}

Otherwise removing an AWS Organization can impact the following ways and we recommend you evaluate each of the impact items for yourself:

<table><thead><tr><th width="214">Impact</th><th>Description</th></tr></thead><tbody><tr><td>Access control</td><td><p>Breaking an organization can affect access control and permissions, which may require additional configuration and management. </p><p></p><p>If you have SSO setup through <a href="https://aws.amazon.com/iam/identity-center/">AWS Identity Center only</a> (see if it is enabled on your end) we recommend you DO NOT disassociate your AWS accounts from your organization.</p></td></tr><tr><td>Cross-account functions management</td><td><p>Managing cross-account functions like logging, security, and monitoring can become more complex when you break an organization. </p><p></p><p>Please proceed here with caution, and check in with us at <a href="mailto:support@usedotted.com">support@usedotted.com</a> or starting an intercom chat.</p></td></tr><tr><td>Account management</td><td><p>Managing multiple accounts separately can be more difficult than managing them within an organization. </p><p></p><p>Dotted sets up a <a href="https://aws.amazon.com/blogs/aws-cloud-financial-management/getting-started-with-aws-billing-conductor/">'billing group'</a> for you to overcome this. </p></td></tr><tr><td>Organizational structure</td><td><p>You may lose the <a href="https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_ous.html">organizational structure (OUs)</a> that you have set up within the organization, which can impact the way you manage and organize your accounts. </p><p></p><p>Dotted can recreate the OUs for you in our organization</p></td></tr></tbody></table>

Bottom line - If you do not have SSO setup for your AWS organization or have communication setup between accounts, we recommend that you break up your organization following these [steps](https://help.usedotted.com/como-comecar/multiplas-contas/via-join-account-s).

However, if you do have it setup or cannot break an organization due to a complex setup, we recommend you to follow the steps [here](https://help.usedotted.com/como-comecar/multiplas-contas/via-join-with-a-pre-existing-org-s).