> 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/how-to/how-to-manage-your-organizations.md).

# How to Manage Your Organizations

Once created, you manage your organizations from **Home > Organizations** and from the **Profile** of each one: you change their details, enter them to work in them, block them, or delete them, and move from one to another. 

The actions for each organization are in the menu (**⋮**) in its row.

> #### 📘 **What are you going to get?** 
>
> Keep your customer portfolio up to date: edit an organization's details, enter it, block it, delete it when you no longer need it, and jump between all of them.

### Before you begin

You need to be logged in and have permission to manage organizations. 

Open **Home > Organizations**.

### Edit an organization

In the organization's row, open the menu (**⋮**) and click **Edit** (or go into it and open **Profile**: they are two ways to the same place). 

You change its details: name, company name, tax ID, address, language, time zone, billing mode, and currency. The **Country** is shown as a reference and is not editable. 

Click **Save** when you're done.

![Editing an organization's details](/files/79fca317ef26ce71d015c47ed18f8c85fb4edccb)

### Enter an organization to work in it

In the menu (**⋮**), click **Go to organization**. 

The notice opens **Manage organization**, which asks you to confirm because the active context changes and you start working in that specific organization. Confirm to enter.

![Confirmation prompt when entering an organization](/files/a12628ae97cae107d497918dd51ec3fdc391adb1)

### Block an organization

In the menu (**⋮**), click **Block**. The notice opens **Block organization**: when you confirm it, its users can no longer access its services. 

The organization remains in your list, with its status reflecting the block.

![Blocking an organization](/files/00dbdd39bcd9c91d2bc68334f9372965e812d303)

> #### ❗️ **Blocking is irreversible** 
>
> The notice itself says so: once blocked, it can't be undone. Use it only if you're sure.

### Delete an organization

You can delete an organization from the menu (**⋮**) with **Delete**, or from its **Profile**, in the block **Delete organization**. In both cases, for security you'll have to type **DELETE** to confirm.

![Deleting an organization](/files/5c0798070e1d64f089cc24fdd7b32c751ad1a365)

> #### ❗️ **Before deleting** 
>
> Cancel all of the organization's subscriptions and make sure you're its administrator. 
>
> It is an irreversible action: it deletes all its data.

### Switch between your organizations

To jump from one organization to another and check your role in each one, you have the step-by-step guide in [How to switch organizations.](/docs-en/platform/organizations/how-to/how-to-create-an-organization.md)

### Conclusion

With these actions you manage the day to day of your portfolio: you edit an organization's details, enter it to work in it, block it when needed, and delete it if you no longer use it. Critical actions ask for confirmation, so it's hard to make mistakes.

### Next steps

* Review the columns and the status of the listing in [Organization list.](/docs-en/platform/organizations/detalles/list.md)
* Check the profile fields in[ Profile.](/docs-en/platform/organizations/detalles/profile.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/how-to/how-to-manage-your-organizations.md?ask=<question>&goal=<endgoal>
```

`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.