> For the complete documentation index, see [llms.txt](https://docs.kemperconnect.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kemperconnect.de/sites/overview.md). # Overview ## Overview Sites (also referred to as workspaces) are the primary organizational unit within the KEMPER Connect platform. Each site represents a distinct physical location, facility, or operational area containing industrial assets and associated monitoring data. ## What is a Site? A site is a logical grouping of: * **Assets**: Industrial devices (sensors, filtration units, extractors) * **Members**: Team members with access to the site * **Configuration**: Site-specific settings and automation rules Typical examples of sites: * Manufacturing plant * Welding workshop * Production hall * Regional facility ## Navigation The site view forms the central navigation layer of the platform. Within a selected site, the left-hand sidebar provides access to all available modules and features, such as dashboards, asset lists, automation, reporting, and other operational tools. Navigation is always contextual to the currently selected site. ## FAQs ### Can I have multiple Sites? Yes, multiple sites can be created. However, site creation is not available directly within the user interface. To create additional sites and manage device distribution across them, please contact platform support for assistance. ### What is the purpose of Sites? Sites allow structured grouping of devices, members, dashboards, automation rules, and operational overviews. They are particularly useful when managing multiple buildings, shop floors, or geographically separated facilities. In such cases, it is recommended to create a separate site for each location to maintain clear operational boundaries and reporting structures. Members can belong to multiple sites and switch between them using the site selector. Automation rules, notifications, and scheduling configurations are defined per site. Therefore, if different facilities require distinct automation logic or alert schedules, separate sites must be configured accordingly. --- # 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.kemperconnect.de/sites/overview.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.