> 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/environment/organizations/creating-an-organization.md).

# Creating an Organization

{% hint style="success" %}

#### Required User Credentials

\[**Flosum User**] - **SystemAdministrator** Role

\[**Salesforce User**] - **Administrator** Credentials&#x20;
{% endhint %}

## ![](https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FSxcnKlaJKPzDqONWoDNv%2FSummary2-Small-Icon.svg?alt=media\&token=5e3253d0-a069-4ba5-9c06-83c70bd0b21d)Overview

To use Flosum Cloud Apps with your Salesforce orgs, you must create an Organization in Global Settings for each Salesforce org you want to connect. This connection enables Flosum to securely communicate with your Salesforce org and perform necessary operations. Before creating the organization, please review the requirements in the following article.

* [Overview of Salesforce Org Requirements](/global-settings/environment/organizations/overview-of-salesforce-org-requirements.md)

This guide offers clear instructions for creating an organization. It is recommended to use a dedicated Salesforce user account specifically to establish the connection between your Salesforce org and Flosum Cloud Apps. The user account needs admin-level permissions to authorize access and grant Flosum the necessary permissions.

{% hint style="info" %}

#### Dedicated Salesforce User

For information about creating the recommended dedicated user, see the following article.

* [Creating a Dedicated Salesforce User](/global-settings/environment/organizations/creating-a-dedicated-salesforce-user.md)
  {% endhint %}

After creating an organization, assign apps to utilize it. See the following article for instructions on assigning apps to organizations.

* [Assigning an App to an Organization](/global-settings/environment/organizations/assigning-an-app-to-an-organization.md)

## Create a Salesforce Organization

{% stepper %}
{% step %}

### Access Global Settings

1. From any **Flosum Cloud App**, click the **App Switcher** icon at the top of the left sidebar menu.

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2Fgh5FcQCnErKAjJ7isiuB%2FGS-Access-01.png?alt=media&amp;token=ddf01506-f133-4e49-825a-76a2a237e3a8" alt="" width="563"><figcaption></figcaption></figure></div>
2. Click **Global Settings**.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2Fx5vntzgpLuT50fMTzwT9%2FGS-Access-02.png?alt=media&amp;token=f67a125f-5087-47c2-9bc6-9393c3d2b7a5" alt="" width="563"><figcaption></figcaption></figure></div>
3. The **Global Settings** app will open in a new tab.

{% hint style="info" %}
Global Settings can also be accessed by logging in directly via the Flosum Cloud Apps Login URL. See the following article for login instructions.

* [Log In To Global Settings](/global-settings/getting-started/log-in-to-global-settings.md)
  {% endhint %}
  {% endstep %}

{% step %}

### Create Organization

1. Click **Organizations** from the sidebar menu.
2. Click **Create**.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FBoqjuoljkOzHqQL7oFGX%2FCreatingAnOrganization-S02-01.png?alt=media&amp;token=97854e79-4ede-45db-a053-0b5f74e48f9e" alt="" width="563"><figcaption></figcaption></figure></div>
3. In the **Name** textbox, enter a descriptive name of the Salesforce org you are connecting to.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FrNWJ24nMew32AKAaA5Ke%2FCreatingAnOrganization-S02-02.png?alt=media&amp;token=a0418384-cd81-4c3d-bc77-cc416b1ceac1" alt="" width="563"><figcaption></figcaption></figure></div>
4. Click the **Organization Type** dropdown.
5. Select the type of instance for the Salesforce org you are connecting to: **Production** or **Sandbox**.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2F4xUqigl2UsWMfMcqQLoo%2FCreatingAnOrganization-S02-03.png?alt=media&amp;token=2ea6c42d-3d9d-4c40-b30f-59e9d19c78d1" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="warning" %}
You must select the correct **Organization Type** for the Salesforce org you are connecting to. This type determines the login method for accessing the org. For example, selecting **Production** for a sandbox org will cause the connection to fail.
{% endhint %}

6. Click the **Environment** dropdown menu.
7. Select the environment label that you want to assign to this organization.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FJB6IaNhgss51Swu351Xb%2FCreatingAnOrganization-S02-04.png?alt=media&amp;token=f232b3bf-dca8-4d25-b883-2156feb80091" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}

#### Environment Label

The **Environment** label helps you identify an organization later. When you have many organizations, the **Environment** label lets you filter and quickly find the ones relevant to your current task. It does not limit the actions that can be performed on or by an organization, and you can change it at any time.
{% endhint %}

8. Click **Create**.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FctmwZ3d9cL1DG3zZUNXF%2FCreatingAnOrganization-S02-05.png?alt=media&amp;token=1fa7f183-e736-4b8e-a7e3-749e12c6b7f0" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}

### Allow Access

{% hint style="info" %}
When connecting a Salesforce org, it is recommended to use a dedicated user. For more information on creating a dedicated user, please refer to the following article.

* [Creating a Dedicated Salesforce User](/global-settings/environment/organizations/creating-a-dedicated-salesforce-user.md)
  {% endhint %}

1. In the **Username** textbox, enter the username of a user with Admin privileges in the Salesforce org you are connecting to.
2. In the **Password** textbox, enter the password for the Salesforce user.
3. Click **Log In**.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FajfCQyFqI2yxQX1D1c3g%2FGSCreatingAConnection-Create-06.png?alt=media&amp;token=0d258063-d6b5-474a-8db4-48088da3a271" alt="" width="375"><figcaption></figcaption></figure></div>
4. Review the items listed in the access request.
5. Click **Allow**.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2Fe97Wt8ZZ4nmBlhrujXH4%2FGSCreatingAConnection-Create-07.png?alt=media&amp;token=2b3a2c65-6a4c-44be-a69c-be3058ebf6b1" alt="" width="375"><figcaption></figcaption></figure></div>
6. The organization you created is now listed in **Organizations**.&#x20;

   <div align="left"><figure><img src="https://579543750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsEk2hU5IMh3HEY5dJZjR%2Fuploads%2FUzAJmvbSphT7VkPpVX71%2FCreatingAnOrganization-S03-03.png?alt=media&amp;token=13792bc5-a89d-4cae-809f-612938a7ba79" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}
{% endstepper %}

## Assigning Apps

When a new organization is created, it initially has no apps assigned to it. You must assign apps to the organization to use them with the Salesforce org. For detailed instructions, refer to the following article on assigning apps to an organization.

* [Assigning an App to an Organization](/global-settings/environment/organizations/assigning-an-app-to-an-organization.md)


---

# 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/environment/organizations/creating-an-organization.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.
