> For the complete documentation index, see [llms.txt](https://docs.i3d.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.i3d.net/organizations/overview-and-settings.md).

# Organization overview and settings

Go to **Organization Management → Overview**. The top of the page shows your **organization name** and **Organization ID**.

{% hint style="info" %}
**The Organization ID is not your account number.** It's the Console's own identifier for your organization — a long string of letters and digits such as `019fefb7-e7df-77a6-8443-f5c80d181c42`. Quote it when i3D.net support asks for it.

Your **account number** is the K-number (`K012345`) on your billing account. That's the one billing and your invoices use, and you'll find it in the **Billing Account** column on the [Servers page](/organizations/servers-page.md).
{% endhint %}

## Organization Settings

Organization settings are available to admins only.

| Field                                | Notes                                                                                                             |
| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
| **Organization name**                | The display name used across the Console. Letters, numbers, spaces, hyphens and underscores; up to 50 characters. |
| **Abuse contact email** *(optional)* | Where abuse notifications should be sent. Leave blank to remove it.                                               |
| **Multi-factor authentication**      | Requires every member to sign in with MFA.                                                                        |

**Save Changes** becomes active once you've edited something, and a confirmation appears when the update succeeds.

{% hint style="info" %}
**MFA is set once, at the top.** The MFA switch can only be changed on your top-level organization, and it applies to every organizational unit beneath it. Inside a unit the switch is shown but greyed out, with a note explaining where to change it. Once MFA is enabled, each member is prompted to enrol the next time they sign in.
{% endhint %}

## Administrators

Lists everyone who holds admin rights, with pagination if there are many. If MFA is enforced, admins can reset a member's MFA enrolment from the [Members](/organizations/members.md) page.

## Danger Zone: Leave Organization

Removes **you** from the organization and signs you out. You'll be asked to confirm first and will lose all access to the organization.

{% hint style="warning" %}
Leaving an organization cannot be undone by you. Ask another admin to re-invite you if you need to come back.
{% endhint %}

## Related topics

* [Organizational units](/organizations/organizational-units.md)
* [Members](/organizations/members.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.i3d.net/organizations/overview-and-settings.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.