> 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/detalles/profile.md).

# Profile

The reference for an organization's data and settings, field by field.

The section **Profile** collects the organization's data and its configuration: its tax identity, language, billing mode, and currency.

This is also where you can delete it.

The header shows its status (**Active** or **Blocked**).

![The Organization Profile section](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2Fgit-blob-68338a8565416b058153947f6300ca88ae5b660b%2FProfile.png?alt=media)

### Company information

| Field             | What it is                                                                  |
| ----------------- | --------------------------------------------------------------------------- |
| Organization name | The name you use to identify the organization.                              |
| Legal name        | The company's legal name.                                                   |
| Tax ID            | The tax ID. It is shown for reference and cannot be edited.                 |
| Country           | The organization's country. It is shown for reference and cannot be edited. |
| Province          | The province. Optional.                                                     |
| Postal code       | The postal code. Optional.                                                  |
| Address           | The address. Optional.                                                      |
| City              | The city. Optional.                                                         |

### Configuration

| Field                      | What it is                                                            |
| -------------------------- | --------------------------------------------------------------------- |
| Language                   | The organization's language.                                          |
| Billing mode               | How the organization is billed (for example, unified).                |
| Time zone                  | The organization's time zone.                                         |
| Currency                   | The billing currency. It is shown for reference and cannot be edited. |
| Enable email notifications | Toggle to enable or disable email alerts.                             |

### Credit

At the end of the section, a table of **Credit** shows the organization's available balance by type (for example, partner incentives or item balance), with its amount and expiration date where applicable.

### Delete the organization

The block **Delete organization** lets you deactivate it.

> #### ❗️ **Before deleting**
>
> Deactivate all of the organization's subscriptions before deleting it, and keep in mind that you must be an organization administrator to do so.
>
> This is an irreversible action.

### Next steps

* Edit this data step by step in [How to manage your organizations.](https://docs.plenit.com/docs-en/platform/organizations/how-to/how-to-manage-your-organizations.md)
* Review what the list shows in [Organization list.](https://docs.plenit.com/docs-en/platform/organizations/detalles/list.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/detalles/profile.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.
