> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/platform/organizations/quickstart.md).

# Quick Start

From zero to operational: understand the dashboard (Home and the Organization level), create the organization, brand it, and add its users with their permissions.

This guide gets you up and running with a new client in just a few minutes.

First you get oriented in the panel, then you create the organization, brand it, and register its users with the correct permissions.

By the end, you'll have a client ready to start deploying services.

> #### 📘 **What will you get?**
>
> Navigate the panel and have a client organization created and configured: with your brand in its portal, its users registered, and their permissions set.
>
> To the client, the service is presented under your identity.

### Before you begin

You need to be signed in and have permission to manage organizations. Have the client's tax details (NIF) at hand and, if you're going to use your own brand, your logo, your main color, and the domain you want to use.

### The panel: where everything is

Everything is navigated from the side menu, structured into three levels. Understanding them saves you from going in circles:

* **Home** — your global view, aggregated across all your organizations.
* **Cloud Services**, **Marketplace** and **IT Management** — the Plenit services catalog.
* **Organization** — the panel limited to the organization you have selected.

#### The Home level: your global view

It brings together, across all your organizations: **Overview** (your activity and counters), **Organizations** (the list of all your client organizations, where you can also create new ones), **Subscriptions**, **Users** and **Events**. It is your personal and global view; its details are documented in Account.

#### An organization's panel

When you enter an organization, you work only with its own items.

It has six sections: **Subscriptions**, **Users**, **Customization**, **Profile**, **Contacts** and **Events**.

![An organization's panel, with its six sections](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-a8f90b7edd5a1399861051fdc6822fd63cf19dad%2FPlenit-Sidebar-Tarjeta.png?alt=media)

### 1. Create your first organization

In **Home > Organizations**, click **New organization** (or **New > Organization** in the top bar).

Fill in the organization details: name, legal name, province, city, address, postal code, language, time zone, billing mode, and industry. If you want, enable email notifications.

When you're done, click **Save**.

![Create an organization](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-4e6674980c6f9d18c6f2eb8e3179056ae8ea1c08%2FCrear_Organizacion.png?alt=media)

The full step-by-step guide is in [How to create an organization.](https://docs.plenit.com/docs-en/platform/organizations/how-to/how-to-create-an-organization.md)

### 2. Enter the organization

To work within that client, select it in the **organization selector** of the side menu or use **Go to organization** from the list, and confirm the prompt.

From there, you operate in its panel, with the six sections you just saw.

### 3. Brand it

In **Customization**, configure the two surfaces the client will see, the **User portal** and the **Administration panel**: logo, favicon, main color, your own domain (with its **CNAME**) and the **certificate** (generate one with Let's Encrypt or upload your own). Also configure the **email**, so that notifications are sent with your identity.

If you send from your own account, remember to enable **SPF and DKIM**.

You have the details in [How to customize the user portal.](https://docs.plenit.com/docs-en/platform/organizations/how-to/how-to-customize-the-user-portal-and-admin-panel.md)

### 4. Register its users and adjust their permissions

In **Users**, register the client's people, one by one or in bulk, following [How to add users.](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-add-users.md)

Then, in the tab **Permissions** for each user, define what they can access: the panel, the organization's sections, each subscription, and, if you want to show them part of your partner operations, those sections.

You can find it in [How to apply permissions to a user.](https://docs.plenit.com/docs-en/platform/accounts/how-to/how-to-assign-user-permissions.md)

### Check that everything is in order

Quick check:

* \[ ] You recognize the three menu levels and know what's in Home and in an organization's panel.
* \[ ] The organization appears in the list with status Active.
* \[ ] Its portal is shown with your brand and, if you configured it, with your domain.
* \[ ] Its users are registered and have the permissions they need.

> #### 👍 **All green**
>
> Your client is ready in Plenit: organization created, branded, and with its users. From here, deploy its services from Subscriptions.

### Next steps

* Understand the model in depth in [Concepts.](https://docs.plenit.com/docs-en/platform/organizations/concepts.md)
* Learn specific tasks in the guides [How-to.](https://docs.plenit.com/docs-en/platform/organizations/how-to.md)
* Check the reference for each section in [Details.](https://docs.plenit.com/docs-en/platform/organizations/detalles.md)
* Resolve common questions in the [FAQ.](https://docs.plenit.com/docs-en/platform/organizations/faq.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.plenit.com/docs-en/platform/organizations/quickstart.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.
