> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/finops-for-cloud/getting-started/access-your-organization.md).

# Access Your Organization

To use [FinOps for Cloud](https://portal.finops.softwareone.com/), you need an account. This account is different from your Marketplace Platform account.&#x20;

When you order a [FinOps for Cloud subscription from the SoftwareOne Marketplace](https://docs.platform.softwareone.com/extensions/finops-for-cloud/order-finops-for-cloud-from-marketplace), we will process your order and create an organization for you. This organization represents your account.

FinOps for Cloud provides different experiences for first-time access, depending on whether you are an organization administrator or user.

### FinOps for Cloud Administrators

Once we process your order, the organization administrator will receive a password recovery email containing a verification code. This email will be sent to the address specified during the ordering process.

To set up a new password and sign in, the organization administrator must follow these steps:

1. Open the password recovery email from SoftwareOne FinOps for Cloud.
2. Select **Recover password**.&#x20;

<figure><img src="/files/vuPVgdkwNbRrQbfjXQxF" alt="" width="563"><figcaption><p>The password recovery email.</p></figcaption></figure>

3. Enter the verification code from the email and select **Confirm**.

<figure><img src="/files/ju7fYPrPBvgFIzTqBBni" alt="" width="484"><figcaption><p>The email verification code.</p></figcaption></figure>

4. Enter your new password and confirm it matches the one you just entered. Then, select **Reset password**.
5. Select **Proceed to FinOps for Cloud** to sign in to your organization.

After signing in, you must connect your data source to FinOps. For more information, see [Add Data Sources](/finops-for-cloud/getting-started/data-sources.md).

### FinOps for Cloud Users

If you've been added to an organization, you'll receive an invitation email from SoftwareOne FinOps for Cloud.

To join your organization:

1. Select the invite link in your email. The registration page opens.

<figure><img src="/files/EXF0Z9i2HrEyUgnooJ2z" alt="" width="473"><figcaption><p>The registration page for FinOps for Cloud.</p></figcaption></figure>

2. Enter your full name and password.&#x20;
3. Confirm that your new password matches the one you entered in the **Password** field, then select **Register**. You'll receive a verification code by email.
4. Enter the verification code to verify your email and select **Confirm**. You'll be directed to FinOps for Cloud.&#x20;
5. Select **Accept** to join your organization and start using FinOps for Cloud.

<figure><img src="/files/K5VJjwOOp9dJY5c017NC" alt=""><figcaption><p>Accept your pending invitation.</p></figcaption></figure>


---

# 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://docs.finops.softwareone.com/finops-for-cloud/getting-started/access-your-organization.md?ask=<question>&goal=<endgoal>
```

`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.
