> For the complete documentation index, see [llms.txt](https://docs.inabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inabit.com/guides/hierarchy-in-inabit.md).

# Hierarchy in inabit

## inabit Account Hierarchy

This page clarifies the relationships between accounts, organizations, and users within the Inabit system.

### **Key Terms:**

* **Account:** Represents a single entity that uses the Inabit system.
* **Organization:** A group of users that belong to the same account. An account can have multiple organizations.
* **User:** An individual who has access to the Inabit system and belongs to a specific organization. An organization can have multiple users. A user can be associated with multiple organizations as well.

### **Relationships:**

* One account can have many organizations (1:N).
* One organization belongs to one account (N:1).
* One organization can have many users (1:N).
* One user belongs to one organization (N:1).

**Example:**

* Inabit Corporation (Account)
  * Marketing Department (Organization)
    * User1 (Marketing Manager)
    * User2 (Social Media Specialist)
  * Sales Department (Organization)
    * User3 (Sales Representative)
    * User4 (Account Manager)


---

# 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.inabit.com/guides/hierarchy-in-inabit.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.