> For the complete documentation index, see [llms.txt](https://docs.devarmor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devarmor.com/modules/threat-modeler/data-model-hierarchy.md). # Data Model Hierarchy The purpose of this document is to clarify the hierarchy of our product data isolation and management. In particular, we cover use cases and workflows to manage threat models and security reviews in organizations based on their size, team composition, and workflows. ## Data Hierarchy ### Organization Organization (“Org”) is the highest level of abstraction in DevArmor’s data model. Org usually correlates to the company as a whole, or a single **unit of risk management**. One way to think about Org is that there is usually one Org per CISO. ### Team A Team is a unit of organization that prioritizes security actions and decisions together. Different teams can share some risks together, or have totally separate risks. The key concept that ties a team together is **planning and prioritization**. A Team roughly corresponds to a unit of organization under a VP or Director of Security. A single organization can have many teams. ### Project A Project is an abstraction layer that corresponds to a product, feature, or service within an organization. A project usually corresponds to a unit of **product development and release schedule**. Alternatively, one can think of a project as a unit of engineering work or organization, such as an engineering team. A single team can have many projects. ### Threat Model A threat model is the lowest level of abstraction in this model, and represents a single body of analysis of risks, threats, mitigation plans, and actors. A project can have multiple threat models. ## Data Isolation DevArmor supports sharing security and product context across projects and teams. This will be set at the Org level. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.devarmor.com/modules/threat-modeler/data-model-hierarchy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.