AssetOps provides flexibility in how you manage and administer maintenance operations, supporting both portfolio-level oversight and building-level execution. This dual-level approach allows you to coordinate strategies across your entire portfolio while addressing the specific needs of individual buildings.
Actions and configurations applied at the portfolio level determine the availability or configuration of resources at the building level. Subsequently, actions performed at the building level are reflected at the portfolio level, ensuring centralized visibility and consistent management across all sites.
Portfolio-Level
The portfolio level in AssetOps provides centralized oversight of all buildings for a client, serving as the main management hub. From this level, you can initially manage and monitor the entire portfolio, while also using it as the entry point to access and manage individual buildings.
In addition, the portfolio level allows configuration of portfolio-wide settings and the management of shared resources, such as vendors, categories, or task templates, ensuring consistent operations and standardized processes across all sites.
Building-Level
At the building level, AssetOps allows you to manage operations for a specific building in detail. You can add and manage assets, create and track work orders, and apply configuration policies defined at the portfolio level.
Building-level operations also include allocating work through routing and dispatch, managing teams, and overseeing day-to-day maintenance activities. All actions performed at the building level flow back to the portfolio level, ensuring complete visibility and consistent oversight across the entire portfolio.
Role-Based Access Implications
Your role in KODE OS determines whether AssetOps is available to you and, if so, defines your specific permissions within the product.
Understanding role-based permissions is essential, as they govern what actions you can perform, which assets and buildings you can access, and how you interact with AssetOps overall.
Creating distinct KODE OS roles for AssetOps can be highly beneficial, allowing you to allocate appropriate levels of access to different users based on their responsibilities.
This approach ensures that users have the tools and visibility they need to perform their tasks efficiently, while control, security, and consistent operational standards are preserved across the organization. Last modified on March 18, 2026
