> For the complete documentation index, see [llms.txt](https://docs.openbrim.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrim.org/templates/concrete-u-girder-bridge-workflow/organization-cug.md). # Organization \[CUG] The **Organization** section can be used to group objects together, enabling their activation or deactivation. By grouping objects, users can activate or deactivate these groups, allowing them to gather FEA results and designs for both the initial model and a secondary model with specific activated or deactivated elements. Additionally, 3D representations, or specific parts of the model such as the substructure, analysis results or other objects from a specific bridge model, can be transferred to different projects using the **Cross-Project Data**. For further explanation and detailed instructions on how to use these features, please refer to the related page. --- # 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.openbrim.org/templates/concrete-u-girder-bridge-workflow/organization-cug.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.