> For the complete documentation index, see [llms.txt](https://docs.north.cloud/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.north.cloud/docs/account-management/settings/add-cloud-accounts.md).

# Add cloud accounts

Learn how to add another cloud account or a SaaS Cost Loop to an organization you have already set up.

You can add accounts at any time after your first one. Open [Settings, then Integrations](https://app.north.cloud/settings?tab=accounts), and click **Add accounts**.

The provider picker shows two groups. **Cloud** holds AWS, Google Cloud, and Azure. **Cost Loops** holds the SaaS providers North supports, such as Snowflake, Anthropic, and OpenAI. You can add from either group, and adding one does not affect the accounts you already have.

## Cloud Accounts

Each cloud provider has its own onboarding guide, with the permissions it needs and the steps to grant them.

{% content-ref url="/pages/uMXDX5flGvRBqdtPXmQ9" %}
[Quickstart](/docs/getting-started/quickstart.md)
{% endcontent-ref %}

## Cost Loops

A Cost Loop brings SaaS spend into North alongside your cloud accounts. Each provider has its own setup guide.

{% content-ref url="/pages/c3A0TWK2bgT0VaU3IMZg" %}
[Cost Loops](/docs/features/cost-loops.md)
{% endcontent-ref %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.north.cloud/docs/account-management/settings/add-cloud-accounts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.