> 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.md). # Organizations Structure your company in the i3D.net Console, give the right people access to the right servers, and consolidate multiple i3D accounts into one organization. {% hint style="info" %} This documentation applies to the i3D.net [Console](https://console.i3d.net/organization). {% endhint %} An **Organization** is your company inside the i3D.net Console. It groups your billing accounts, your servers, and the people who are allowed to see them. Every customer has one. If you have never done anything with organizations, one was created for you automatically the first time you signed in — you don't need to set anything up, and nothing about your day-to-day work changes. Organizations become useful when you are more than one team. Instead of running several separate i3D accounts and sharing logins between developers, you can: * **Describe your real structure** — create organizational units for studios, departments, regions or teams inside your organization. * **Invite people once** — a member invited at one point in the structure automatically has access to everything beneath it. * **See a joined-up view** — from the top of your structure you see every server across every unit; from a single unit you see only that unit's servers. * **Bring existing accounts together** — if your company has ended up with several separate i3D accounts over the years, you can consolidate them into one organization. {% hint style="warning" %} **Known limitation: billing is not yet organization-aware.** Today, each billing account (K-number) in your organization is invoiced **separately**, exactly as it was before you had an organization — including accounts brought in through an [import](/organizations/importing-an-organization.md). Grouping servers and people under one organization does not group their invoicing. Consolidated invoicing across an organization is planned, but not available yet. If you need a single invoice across several accounts today, contact your i3D.net account manager. {% endhint %} ## How access works Two rules explain almost everything: 1. **Access flows downward, never upward or sideways.** A member added to *Studio A* can see *Studio A* and everything underneath it. They cannot see a sibling *Studio B* node, even though both sit under the same parent. Someone added at the top of your organization can see everything. 2. **You are added at exactly one place.** Where someone is added decides what they can see. If a colleague should see one studio only, invite them to that studio — not to the top of your organization. ## Key terms | Term | What it means | | ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Organization** | Your company in the Console. Owns billing accounts, servers, and members. | | **Organizational unit** | A team, studio, department or region inside your organization. Behaves like an organization in its own right and can have organizational units of its own. | | **Organization ID** | The Console's own identifier for your organization — a long string of letters and digits, for example `019fefb7-e7df-77a6-8443-f5c80d181c42`. Shown under your organization name. It is **not** your account number, and billing does not use it. | | **Billing account / K-number** | Your account number, for example `K012345`. This is the identifier i3D.net billing recognizes, and it belongs to a billing account rather than to the organization. An organization can hold more than one — see [Importing an organization](/organizations/importing-an-organization.md). | | **Member** | Anyone with access to your organization or one of its organizational units. | | **Admin** | A member who can change settings, invite people, manage members and create organizational units. You can have more than one. | | **Owner** | The person who originally created the organization. Shown for reference — it isn't a permission level. | | **Invitation** | An email that lets someone join your organization. It expires if it isn't used. | | **Import / combine** | Bringing another i3D organization hierarchy — its billing account, servers and members — into yours. | ## Finding your way around **Left-hand navigation** * **Services → Servers** — your server list. * **Organization Management → Overview** — your organization's name, ID, settings, administrators and structure. * **Organization Management → Members** — the people in your organization, and the invitations you've sent. * **My Profile** — your user details. **Organization switcher (top of the page)** The switcher shows the organization or organizational unit you are currently working in. Everything on screen — servers, members, settings — is shown for this organization. The switcher is the main component you use to navigate between the organizational units in your organization. * Click it to see everything you have access to, grouped by top-level organization. * If you have more than five, a search box appears. * Selecting a different one shows a short *Switching Organization* screen and then reloads the page in the new context. If you only belong to one organization, the switcher simply shows its name. ## Related topics * [Organization overview and settings](/organizations/overview-and-settings.md) * [Organizational units](/organizations/organizational-units.md) * [Members](/organizations/members.md) * [Inviting a member](/organizations/inviting-a-member.md) * [Importing an organization](/organizations/importing-an-organization.md) * [The Servers page](/organizations/servers-page.md) * [Server details](/organizations/server-details.md) * [Server labels](/organizations/server-labels.md) * [Traffic alerts](/organizations/server-traffic-alerts.md) * [Server usage](/organizations/server-usage.md) * [Troubleshooting and FAQ](/organizations/troubleshooting.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.md?ask=&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.