> For the complete documentation index, see [llms.txt](https://docs.icepanel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.icepanel.io/core-features/modelling/model-objects-view.md). # Model objects view Model objects can be viewed in a list format in the Model Objects view. Navigate to this page from the left-hand menu in the home screen. ## Adding objects in the model objects view

Here, you can quickly add and view your model objects in your domain. You can also search for and sort by tags, diagram count, description added, etc. **Visible by default:** * Actors, Systems and Groups **Expand systems to view:** * Apps and Stores **Expand apps and stores to view:** * Components You can add, edit, and delete objects from here. You can also view and edit the details of each object, just like in a diagram. {% hint style="success" %} You can duplicate any object in the model object list by right-clicking it and selecting the *Duplicate object* option. {% endhint %}

## Filtering in the model view

Filtering options in model objects section

You can filter your model objects based on: * Technology choices * Status * Live * Future * Deprecated * Removed * Team ownership `(Growth plan only)` * Tags (custom) * Type * Internal * External * System * Actor * Group * App * Store * Component * Diagram * In a diagram * In a flow * Details * Has a display description * Has a detailed description --- # 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.icepanel.io/core-features/modelling/model-objects-view.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.