> 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 This guide gets you up and running with a new client in just a few minutes. First you navigate the dashboard and then create the organization, brand it with your own identity, and register its users with the correct permissions. When you're done, you'll have a client ready to start deploying services. > #### 📘 **What will you achieve?** > > Navigate the dashboard and have a client organization created and configured: with your branding in its portal, its users registered, and their permissions set correctly. > > From the client's point of view, the service is presented with your identity. ### Before you start You need to be logged in and have permission to manage organizations. Have the client's tax details (NIF) ready and, if you're going to use your own branding, your logo, your main color, and the domain you want to use. ### The dashboard: 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** — Plenit's service catalog. * **Organization** — the dashboard limited to the organization you have selected. #### The Home level: your global view It brings together, across all your organizations: **Summary** (your activity and counters), **Organizations** (the list of all your client organizations, where you also create new ones), **Subscriptions**, **Users** and **Events**. It is your personal, global view; its details are documented in Account. #### The dashboard of an organization When you enter an organization, you work only with its own items. It has six sections: **Subscriptions**, **Users**, **Customization**, **Profile**, **Contacts** and **Events**. ![The dashboard of an organization, with its six sections](/files/2f04dcf274e0e22d4acdceab64374cdbb94ef6ad) ### 1. Create your first organization In **Home > Organizations**, click **New organization** (or **New > Organization** in the top bar). Fill in the organization's details: name, legal name, province, city, address, postal code, language, time zone, billing mode, and sector. If you want, enable email notifications. When you're done, click **Save**. ![Create an organization](/files/e532372da1ea76315e914d2e9cbf27482001bc88) The full step-by-step is in [How to create an organization.](/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** in the side menu or use **Go to organization** from the list, and confirm the notice. From then on you operate in its dashboard, with the six sections you just saw. ### 3. Brand it with your identity In **Customization**, configure the two surfaces the client will see, the **User Portal** and the **Admin 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 notices 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.](/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 register users. ](/docs-en/platform/accounts/how-to/how-to-add-users.md) Then, in the **Permissions** tab of each user, define what they can access: the dashboard, the organization's sections, each subscription, and, if you want to show part of your partner operations, those sections. You can find it in [How to apply permissions to a user.](/docs-en/platform/accounts/how-to/how-to-assign-user-permissions.md) ### Check that everything is in order Quick review: * \[ ] You recognize the three menu levels and know what is in Home and in an organization's dashboard. * \[ ] The organization appears in the list with Active status. * \[ ] Its portal is shown with your branding and, if you configured it, with your domain. * \[ ] Its users are registered and have the appropriate permissions. > #### 👍 **All green** > > Your client is ready in Plenit: organization created, with your branding and with its users. From here, deploy its services from Subscriptions. ### Next steps * Understand the model in depth in [Concepts.](/docs-en/platform/organizations/concepts.md) * Learn specific tasks in the [How-to.](/docs-en/platform/organizations/how-to.md) * Consult the reference for each section in [Details.](/docs-en/platform/organizations/detalles.md) * Resolve common questions in the [FAQ.](/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 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.plenit.com/docs-en/platform/organizations/quickstart.md?ask=&goal= ``` `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.