> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/overview/organizations/organization-management.md).

# Organization Management

The Management area allows you to manage plans within an organization, monitor GIGS consumption, distribute GIGS, delete an organization, etc. 

After accessing the “ Management ” menu, the screen displays the following data:

* **Organization Name**
* **Number of workspaces linked to the Organization**
* **Organization ID**

<figure><img src="/files/Es0rNC1pMahO0lPRT5XY" alt=""><figcaption></figcaption></figure>

#### Plan and consumption

In this block, you can view your plan details and data consumption:

* **Plan + plan name**: shows details of the type of plan you have (e.g. monthly, etc.).
* **Data usage**: according to usage, the graph shows the amount of GIGS used.
* **Renew on**: shows the plan's renewal date.

**Additional GIGS**

You can configure the use of additional GIGS for when your plan expires.

After enabling the option, click the edit icon (pencil) to specify how many GIGS can be added after the end of your contracted plan. You can adjust the value using the sliders or manually enter the desired number for each workspace.

To complete the configuration, click "**Save**".

#### Plans

View data and activate new plans in this block. [Read more about Plans here](/english/skyone-studio/overview/settings-and-preferences/usage-and-billing.md#planos).

{% hint style="warning" %}
When activating a new plan for the organization, it will replace the previous plan. GIGS are not accumulated but overwritten by the new value.

Example: If the organization had 15 GIGS and you activate a 10 GIGS plan, the new total will be 10 GIGS, evenly distributed across the workspaces.
{% endhint %}

#### Distribute GIGS&#x20;

When creating an organization, the GIGS from all added workspaces are combined and managed centrally.

<figure><img src="/files/fiuOiB5578nwJkkH7r3Q" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The distribution of GIGS is based on the remaining amount rather than the original total of the plan. In other words, if a workspace has already used part of the GIGS, that used amount will be included in the total sum.
{% endhint %}

The initial distribution of GIGS is done equally among the workspaces. However, in this area, you can distribute the organization’s GIGS in the most convenient way.

To do this, simply adjust the GIGS for each workspace using the sliders or manually enter the desired number.

{% hint style="info" %}
It is necessary to allocate 100% of the available GIGS.
{% endhint %}

#### Delete Organization

To delete an Organization, click the "**Delete Organization**" button.&#x20;

A confirmation screen will appear. To confirm, type the Organization's name in the designated field and then click "**Delete**".

<figure><img src="/files/vfsDMBNFhvToSn99sEHb" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Important: When you delete the organization, the management of the workspaces will shift from centralized to individual. As a result, all workspaces will revert to their initial status, with 0 GIGS, and you will need to reactivate the plans for each workspace.
{% endhint %}


---

# 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:

```
GET https://docs.skyone.cloud/english/skyone-studio/overview/organizations/organization-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.