> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/global-settings/getting-started/register-a-flosum-cloud-apps-tenant.md).
# Register a Flosum Cloud Apps Tenant
## Overview
To get started with Flosum Cloud Apps, you must first register a tenant for your organization. This registration process serves as the foundation for accessing all Flosum Cloud Apps. Once your tenant is registered, you can proceed to add Backup & Archive and any other Cloud Apps that meet your organization's needs.
Once you've completed registration, you're ready to configure your tenant. This involves adding Salesforce organizations to Global Settings and adding users so team members can access the platform.
{% hint style="info" %}
You can activate a 14-day free trial of Backup & Archive to test the product's features and determine whether it suits your organization. You can upgrade to a paid license at any time by contacting your Flosum Success Manager or submitting a case using the following link.
* [Flosum Success Portal - Open Case](https://success.flosum.com/s/login/?ec=302\&startURL=%2Fs%2Fnew-case)
{% endhint %}
## Self-Register
{% stepper %}
{% step %}
### Register New Tenant
{% hint style="info" %}
The user registering a tenant will become the tenant’s System Administrator.
{% endhint %}
1. Open your browser and go to:
2. Click the **Register now** link.
3. Identify the appropriate region to store your Flosum Cloud Apps data based on your data residency and compliance requirements.
4. Click your desired region.
5. Enter the following details to create your tenant:
* **First name**: Your first name.
* **Last name**: Your last name.
* **Email**: Your email address to use for logging in and receiving verification emails. Must be a business email address.
* **Password**: Use a strong password with a minimum of 8 characters, including at least 1 letter, 1 number, and 1 special character.
6. Click **Sign Up**.
{% endstep %}
{% step %}
### Verify Email
1. A verification email is sent to the email address provided on the registration screen.
2. Access your email account and open **Flosum: Please verify your email**.
{% hint style="info" %}
The email is sent from ****. Check your spam folder if you have not received the email.
{% endhint %}
3. Click the **Verify Your Email** link.
{% endstep %}
{% step %}
### Complete Registration
1. Enter the email you signed up with in the **Email** textbox.
2. Click **Continue**.
3. Access your email account and open **Flosum: Login Verification Code**.
{% hint style="info" %}
The email is sent from ****. Check your spam folder if you have not received the email.
{% endhint %}
4. Copy the verification code.
5. Enter the copied verification code in the **Verification Code** textbox.
6. Click **Continue**.
7. Click the tenant you created.
{% hint style="info" %}
If you have multiple tenants, find the tenant name in **Flosum: Please verify your email** message you received during registration. You can change the tenant name in the Global Settings app after registration is complete.
{% endhint %}
8. In the **Password** textbox, enter the password you created.
9. Click **Login**.
10. You will be logged in to **Global Settings**.
{% endstep %}
{% endstepper %}
---
# 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.flosum.com/global-settings/getting-started/register-a-flosum-cloud-apps-tenant.md?ask=&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.
