# Your first organization and workspace

In Ninox, the way you structure your data and apps is organized into two main levels: **organization** and **workspaces**. Understanding these levels helps you manage your team, apps, and data efficiently.

An **organization** is the top-level container in Ninox. It acts as the home base for your team, bringing together all your workspaces under one roof. Within your organization, you can:

* Manage users and assign roles
* Set organization-wide settings
* Oversee all workspaces and their contents

Think of your organization as your company or main entity in Ninox. For example, you might have one organization for your business and another for your voluntary work.

A **workspace** sits within an organization. Workspaces are where you create and run your apps. Each workspace is independent, holding its own:

* Apps
* Data
* Settings

This separation allows you to keep different solutions or projects clearly organized. For example, within your organization, you might have separate workspaces for:

* HR
* Company events
* Development projects
* Sports club activities
* Charity work

Each workspace can contain multiple apps, and each app manages its own tables, records, and settings.

Here is how your Ninox environment might be structured:

{% tabs %}
{% tab title="Organization 1: My company" %}

<table data-card-size="large" data-view="cards"><thead><tr><th>Workspace</th><th>Apps</th></tr></thead><tbody><tr><td>HR</td><td><ul><li>Onboarding</li><li>Vacation planner</li><li>...</li></ul></td></tr><tr><td>Company events</td><td><ul><li>Event planning</li><li>Guest lists</li><li>...</li></ul></td></tr></tbody></table>
{% endtab %}

{% tab title="Organization 2: My voluntary work" %}

<table data-card-size="large" data-view="cards"><thead><tr><th>Workspace</th><th>Apps</th></tr></thead><tbody><tr><td>Sports club</td><td><ul><li>Memberships</li><li>Scheduling</li><li>...</li></ul></td></tr><tr><td>Charity work</td><td><ul><li>Donation tracking</li><li>Volunteer coordination</li><li>...</li></ul></td></tr></tbody></table>
{% endtab %}
{% endtabs %}

Let's recap this:

* An organization can have multiple workspaces.
* Each workspace is independent and can have its own apps and data.
* Users and roles are managed at the organization level, but access can be controlled per workspace.

This structure helps you keep your solutions organized, secure, and easy to manage as your needs grow.

## Creating an organization and workspace in Ninox <a href="#creating-an-organization-and-workspace-in-ninox" id="creating-an-organization-and-workspace-in-ninox"></a>

There are two alternative ways to set up organizations and workspaces in Ninox.\
The first one is the [automated onboarding](#automated-way-during-onboarding) flow, which guides you through creating your first organization and workspace. This ensures you are ready to start building right away.\
The second way is to create additional organizations and workspaces [manually](#manual-way-after-onboarding).\
This flexibility allows you to structure your Ninox environment to fit your needs, whether you are just starting out or expanding your setup.

### Automated way during onboarding <a href="#automated-way-during-onboarding" id="automated-way-during-onboarding"></a>

When you sign up for Ninox, you are guided through an onboarding flow. During this process:

* You are asked to enter an **Organization name** and a **Workspace name**.
* Ninox uses these names to automatically create your first organization and workspace.
* After onboarding, you land in your new workspace and can immediately start building your first app.

**Tip:** You can edit the organization and workspace names later in the **Settings** screen.

### Manual way after onboarding <a href="#manual-way-after-onboarding" id="manual-way-after-onboarding"></a>

You can also create additional organizations and workspaces at any time, independently of the onboarding flow.

To create a new organization manually:

{% stepper %}
{% step %}
**Open Settings**

Click **Settings** in the main navigation.
{% endstep %}

{% step %}
**Open the organization selector**

In the **ORGANIZATION** section, click the current organization name.
{% endstep %}

{% step %}
**Start organization creation**

Select **+ Create organization**.
{% endstep %}

{% step %}
**Enter the organization details**

Enter a **Name**.

Ninox generates the **Internal name** automatically. You can change it, but this is not recommended.

Click **Create organization**.
{% endstep %}
{% endstepper %}

Your new organization is now available in **Settings**. Next, create a workspace inside it.

To create a new workspace manually:

{% stepper %}
{% step %}
**Select the organization**

In the **ORGANIZATION** section, select the organization where you want to add the workspace.
{% endstep %}

{% step %}
**Open the workspace selector**

In the **WORKSPACE** section, click the current workspace name.
{% endstep %}

{% step %}
**Start workspace creation**

Select **+ Create workspace**.
{% endstep %}

{% step %}
**Enter the workspace details**

Enter a **Name** for your new workspace.

Ninox generates the **Internal name** automatically. You can change it, but this is not recommended.

Click **Create workspace**.
{% endstep %}
{% endstepper %}

You now have created a new workspace and are ready to continue configuring tables and fields.

{% hint style="info" %}
You can always manage and edit organization and workspace properties, such as name, color, and members from the **Settings** screen. Click the **gear icon** <i class="fa-gear">:gear:</i> in the main navigation to access the settings.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.ninox.com/getting-started/builder-getting-started/set-up-your-ninox-manually/your-first-organization-and-workspace.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
