> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/end-users/library/exploring-the-library-structure-and-hierarchy.md). # Understanding Documentation Structure Understand the modules, object types, and parent-child relationships that define the Library's structure and organization. The **Library** is organized into **ten modules**, each designed to support a specific function in managing your organization’s knowledge, documentation, and operations. *** ## What are the Library Modules? Below is an overview of the ten modules and their purposes: 1. **Process** Workflows, procedures, and operational sequences that define how tasks are performed. 2. **Document** Files, reports, and reference materials that support processes. 3. **Performance** Objectives, metrics, indicators, and measurement frameworks used to track organizational effectiveness. 4. **Organization** Organizational units, departments, roles, resources, and assets. 5. **Risk** Identified threats, vulnerabilities, and potential impact scenarios. 6. **Control** Safeguards, policies, and measures that mitigate risks. 7. **Rule** Business rules, regulations, and compliance requirements. 8. **Master Data** Authoritative reference data and standards used organization-wide. 9. **Capability** Skills, competencies, and functional abilities within the organization. 10. **Glossary** Definitions and terminology to ensure consistent understanding across teams. *** ## How Do Modules Organize Content? * Each module contains **folders** and **objects**. * Folders and objects can be **nested** to create hierarchical structures that improve organization and ease navigation. *** ## What Are the Object Types & Parent-Child Relationships? Each module supports specific **object types** with defined **parent-child relationships**.
ModuleObject TypeParent Object(s)
Process ProcessFolder or Process
Flow Object (Event, Task, Gateway, etc.)Process
DocumentDocumentFolder or Document
PerformanceObjectiveFolder or Objective
Performance IndicatorObjective or Performance Indicator
OrganizationOrganization UnitFolder or Organization Unit
RoleOrganization Unit
ResourceOrganization Unit
AssetOrganization Unit
RiskRiskFolder
ControlControlFolder
RuleRuleFolder
Master DataEntityFolder
AttributeFolder
CapabilityCapabilityFolder
GlossaryTermFolder
*** ## What are Examples of Common Object Hierarchies? To better understand how modules are structured, here are examples of typical object hierarchies: {% tabs %} {% tab title="Process" %} **Process Folder:** Employee Onboarding * **Process:** New Hire Orientation * **Flow Object (Start Event):** Start Orientation * **Flow Object (Task):** HR Document Verification * **Flow Object (Gateway):** Eligibility Check * **Flow Object (Task):** IT Setup * **Flow Object (End Event):** Orientation Completion {% endtab %} {% tab title="Document" %} **Document Folder:** Marketing Materials * **Document Folder:** Product Brochures * **Document:** 2025 Product Line Brochure * **Document:** Pricing Guide * **Document:** Marketing Strategy Report 2025 {% endtab %} {% tab title="Performance" %} **Performance Folder:** Sales Objectives * **Objective:** Increase Q3 Revenue * **KPI:** Monthly Sales Volume * **KPI:** Customer Acquisition Rate * **KCI:** Referral Conversion Rate {% endtab %} {% tab title="Organization" %} **Organization Folder:** Corporate Headquarters * **Organization Unit:** Marketing Department * **Role:** Marketing Manager * **Role:** Content Specialist * **Resource:** John Doe * **Asset:** Company Laptop * **Organization Unit:** IT Department * **Role:** IT Support Technician * **Resource:** Jane Doe * **Asset:** Network Router {% endtab %} {% tab title="Risk" %} **Risk Folder:** Cybersecurity Risks * **Risk:** Phishing Attack * **Risk:** Data Breach * **Risk:** Ransomware Infection {% endtab %} {% endtabs %} *** ## See Also
How to View DocumentationFind, view, and interact with your organization's documentation.IMS-V16-NAV-Library-Icons-16.pngViewing Documentation
How to Navigate the LibraryLearn how to move through the Library using the navigation tree, breadcrumb trail, and List View.IMS-V16-NAV-Library-Icons-13.pngNavigating the Library
How to Tailor the List ViewCustomize the List View to display relevant information and organize content.IMS-V16-NAV-Library-Icons-28.pngManaging & Customizing the List View
--- # 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://interfacing.gitbook.io/interfacing-help-files/end-users/library/exploring-the-library-structure-and-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.