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

# Troubleshooting and FAQ

**Do I have to use organizational units?**\
No. If you're a single team, carry on as you are — one organization is a perfectly good setup. Add [organizational units](/organizations/organizational-units.md) when you actually need to separate teams.

**Does an invited member see everything I see?**\
They see the organization you invited them to and everything beneath it. They don't see anything above it or alongside it. To limit someone to one studio, invite them to that studio.

**Someone needs access to two studios that don't share a parent.**\
Invite them to each one separately, or invite them at a level above both if they should see everything underneath it.

**Why can't I remove this member?**\
The organization Owner can't be removed, and neither can **Core** members — their organization was merged into yours. See [Members](/organizations/members.md).

**Why is the MFA switch greyed out?**\
MFA is controlled by your top-level organization and applies to every organizational unit beneath it. Change it there — see [Organization overview and settings](/organizations/overview-and-settings.md).

**I invited the wrong person.**\
Go to **Members → Invitations**, open the ⋮ menu on that row and choose **Delete Invitation**. If they've already accepted, remove them from the **Members** tab instead.

**The invitation expired before they used it.**\
Send a new one — there's no need to wait for the old one to clear.

**My Organization ID doesn't look like my account number.**\
It isn't one. The **Organization ID** shown under your organization name identifies your organization inside the Console and is a long string of letters and digits. Your **account number** is the K-number (`K012345`) on your billing account, shown per server in the **Billing Account** column on the [Servers page](/organizations/servers-page.md). Billing only ever uses the K-number.

**Does my organization give me a single invoice?**\
Not yet. Each billing account (K-number) in your organization is invoiced separately, and organizations don't currently group invoicing the way they group servers, members and access. Consolidated invoicing is planned but not available yet — if you need one invoice across several accounts today, contact your i3D.net account manager.

**Will importing an organization change my invoices?**\
No. Each account keeps receiving its own invoices, and each server keeps showing its original account number in the **Billing Account** column on the [Servers page](/organizations/servers-page.md).

**I don't see the Import organization button.**\
It's an admin-only action. Ask an administrator of your organization to run the import, or to make you an admin.

**I need more than ten levels or more than twenty organizational units under a single parent.**\
Raise a support case — the limits can be increased for your organization.

{% hint style="info" %}
Need help? Use the **Need Help** option in the Console footer, or contact your i3D.net account manager.
{% 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 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/troubleshooting.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.