> 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/accounts/quickstart.md).

# Quick Start

Learn the three levels of the dashboard, complete your profile, and secure your account.

This guide gets you up and running in a few minutes.

You get oriented in the dashboard, complete your profile, and secure your account. When you finish, you'll move around the platform with ease and have your account ready to work.

> #### 📘 What will you achieve?
>
> When you finish, you'll know the three dashboard levels, have your profile complete (name, position, language, and time zone), have secured your account with your own password and your security emails, and know where to check the organizations you belong to and your role in each one.

### Before you begin

You need an account in Plenit and to be logged in. If you arrived via an invitation, sign in with your email and the password you set when activating your account.

### 1. Get to know the dashboard and its three levels

When you log in, everything is organized in the **side menu**, structured in three levels:

1. **Home** — your global view. It brings together, aggregated across all your organizations: **Overview**, **Subscriptions**, **Users** and **Events**.
2. **Cloud Services**, **Marketplace** and **IT Management** — Plenit's services, with a cross-cutting view of what you have contracted and what you can contract.
3. **Organization** — the level limited to a single organization, the one you have selected. From here you manage its **Subscriptions**, **Users**, **Customization**, **Profile**, **Contacts**, **Events** and the **Partner Zone**.

The key difference: **Home** gives you the global picture, everything that is yours; the **Organization** level focuses you on a specific company. That's why Subscriptions, Users, and Events appear in both places, with different scope. The **Organization** and the management of your organizations are documented in their own section; here we focus on your account.

![Side menu with the three navigation levels](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-3b7fab3df350a817eef4cfc571270a4c562f546a%2F3___NIveles.png?alt=media)

Your profile and session are in the **user menu**, at the bottom left: click your name to open **My Profile**, change the theme (light or dark), or log out.

Open the **user menu** and go into **My Profile**. In the tab **Profile**, fill in your details:

* **Name** and **Surnames**.
* **Position** and **Phone**. They are optional and help identify you within your organization.
* **Language** and **Time zone**. They determine how you see the platform and how dates are displayed.
* In **Other contact details**, choose between using those of your main organization or defining your own data for your user.

The **Email** and the **Last access** (with its IP) appear as reference and cannot be edited. When you're done, click **Save**.

![Profile tab in My Profile with the user's details](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-30021a0f0a9fb5798184ba90a191a318626c2fe0%2FProfile.png?alt=media)

### 3. Secure your account

In **My Profile**, open the tab **Security**. It has three sections:

* **Change password** — enter your current password, type the new one twice, and click **Save**.
* **Security emails** — add one or more addresses to recover access and receive security alerts.
* **Delete user** — delete your user from Plenit.

To get your account ready, change the password to your own and add at least one security email.

> #### ❗️ Deleting a user is an irreversible action
>
> The section **Delete user** deletes your user permanently and cannot be undone. Use it only if you're sure. We explain it in Details.<br>

![Security tab with the password change](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-8a85b1f946d8cde27013e35a7ca3b8c8a85fa646%2FSecurity.png?alt=media)

### 4. Review your organizations and your role

You're still in **My Profile**: open the tab **Organizations**. Here you see **the organizations you belong to** and, next to each one, your **permission** (for example, Administrator). If you have many, use the search by name.

This list is your personal map: it tells you which organizations you're in and with what role. To enter and work in one, select it from the **Organization** selector in the side menu.

![Organizations tab with the user's role in each one](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-1b0253eca1874a133379c28fd8d20a423cfb2e9d%2FOrganizaciones.png?alt=media)

> #### 📘 This list is only your personal view
>
> In **My Profile**, the tab **Organizations** shows **your** organizations and **your role**, in read-only mode.
>
> **Managing** organizations—creating them, editing them, or entering one—is done from its own section, **Organizations**. We clarify it in Concepts.

### 5. Check your activity in Events

Finally, in My Profile open the tab **Events**. It is the record of your activity: each action is logged so you can review it later.

Each event shows three pieces of data, and you can sort by any of them:

* **Area** — the part of the platform where it happened (for example, Servers).
* **Message** — what happened, with a status icon: green if it was successful, red if there was an error.
* **Created** — the date and time.

With **Filters** narrow the list to find what you're looking for.

<i class="fa-person-to-portal">:person-to-portal:</i> This is **your** a personal record, within My Profile. Each organization also has its own Events, with that company's activity. You'll see it in its section.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-9f9c10e3d3149eac89ff80af8984d521bd956036%2FEventos.png?alt=media" alt=""><figcaption></figcaption></figure>

### Check that everything is in order

Quick recap:

* You recognize the three menu levels: Home, Services, and Organization.
* Your profile has a name, language, and time zone, and you've saved it.
* You changed the password and added a security email.
* You know where to see your organizations and your role.

> #### 👍 Everything is green
>
> Your account is ready and you move around the dashboard with ease. What you do from here on starts from this foundation.

### Next steps

* Understand in depth how the account and organizations relate in [**Concepts**](https://docs.plenit.com/docs-en/platform/accounts/concepts.md)
* Learn specific tasks (editing your profile, setting up your security emails, registering users, checking your events) in the [**how-to guides**.](https://docs.plenit.com/docs-en/platform/accounts/how-to.md)
* Check the reference for fields and statuses in[ **Details**.](https://docs.plenit.com/docs-en/platform/accounts/details.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/accounts/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.
